Skip to content

Update RELEASING.md to fix tag confusion in release process #150

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
rgrnwd merged 1 commit into from
Feb 6, 2026
+4 −5
Merged

Update RELEASING.md to fix tag confusion in release process #150

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
9 changes: 4 additions & 5 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,17 +27,16 @@ Releasing
gradle.properties
```

5. Tag the release and push to GitHub. Submit and merge PR.
5. Submit and merge PR.

```sh
git commit -am "Prepare for release $RELEASE_VERSION."
git tag -a v$RELEASE_VERSION -m "Version $RELEASE_VERSION"
git push && git push --tags
git push
gh pr create -f && gh pr merge --auto --squash
```

6. Wait until the PR created above is merged, then trigger the
[Publish a release](https://github.com/cashapp/quiver/actions/workflows/Release.yml) action against the new tag.
6. Wait until the PR created above is merged, then create a new release via the [GitHub UI](https://github.com/block/quiver/releases/new)
You will need to manually create the tag, ensuring that it starts with v (e.g. v1.0.0)
This will publish to [Sonatype Nexus](https://oss.sonatype.org/), closing and releasing the artifact
automatically to promote it to Maven Central. Note that it can take 10 to 30 minutes or more for the
artifacts to appear on Maven Central.
Expand Down
Loading