Skip to content

ci: remove the bump-version workflow #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arv merged 1 commit into from
Oct 19, 2026
+6 −47
Merged

ci: remove the bump-version workflow #56

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 0 additions & 41 deletions .github/workflows/bump-version.yml
View file
Open in desktop

This file was deleted.

12 changes: 6 additions & 6 deletions docs/contribution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,11 +137,11 @@ People love `better-sqlite3` because of its robustness and reliability. Each and

Trusted contributors have the privileges necessary to create a release. Here are the steps to create a release:

1. Run [this workflow](https://github.com/WiseLibs/better-sqlite3/actions/workflows/bump-version.yml) from the `master` branch to create a new version tag
- Select `patch` for bug fixes and general maintenance
- Select `minor` for larger releases with new features
- Select `major` for releases with backwards-incompatible changes
2. [Draft a new release](https://github.com/WiseLibs/better-sqlite3/releases/new), and select the version tag that you just created
1. Open a pull request that bumps `version` in `package.json` (e.g. `npm version patch --no-git-tag-version`), and merge it through the merge queue
- Bump `patch` for bug fixes and general maintenance
- Bump `minor` for larger releases with new features
- Bump `major` for releases with backwards-incompatible changes
2. [Draft a new release](https://github.com/rocicorp/zero-sqlite3/releases/new) with a new tag `v<version>` on the merged commit
3. Leave the "Release title" blank, and click "Auto-generate release notes"
4. Click "Publish release"
5. Wait for the `build` job to complete ([here](https://github.com/WiseLibs/better-sqlite3/actions))
5. Wait for the `build` job to complete ([here](https://github.com/rocicorp/zero-sqlite3/actions/workflows/build.yml))
Loading