Post

and the equally fun "when are you going to release this?" 🤡

Writing "any update on this?" is a good way to have me not look into something 🤡

I never got this question because we auto release every PR as patch or minor. Makes it easy to understand which PR is responsible for a regression once you've narrowed it down to a specific version. And no need to manually cut releases. 10/10, can recommend.

24/5/25, 6:41 pm0 reposts2 likes

Igal Klebanov 💥 kysely

@igal.dev

24 May 2025

we have @pkg.pr.new for that. pushing preview builds for PRs, the long-living `next` branch, etc. people can play around with these or the playground. there were a few times where we rolled back and redesigned an API idea before release. if that would have hit `latest` on `npm` prematurely - ouch.