-
-
Notifications
You must be signed in to change notification settings - Fork 832
Maintainer notes
Daniel Lockyer edited this page May 8, 2025
·
1 revision
In order to release a new version, you can:
- Change the package.json
version
+ create a commit - Create a tag at this commit -
git tag v5.x.x
- Push the commit and tag to
master
-git push --follow-tags
- Wait until CI has created all the prebuilt binaries
- Run
npm release
- Create the GitHub release
Unfortunately, as of May 2025, the CI workflows for building prebuilt binaries is broken because of runner OS deprecations and bumps. You'll first need to fix this.
- Go to the SQLite download page
- Download the latest
sqlite-autoconf-XXXXXXX.tar.gz
file - Replace the existing one in
deps/
- Update the version in
deps/common-sqlite.gypi
- Update the README
- Commit this (ideally with a locally calculated sha3-256sum that matches the one on the download page)
An example commit is here.