Repository navigation
chore: prepare release v3.1.0 - #501
Open
calvinbrewer wants to merge 3 commits into
Open
calvinbrewer wants to merge 3 commits into
calvinbrewer wants to merge 3 commits into
Conversation
The v3.0.2 GitHub release was cut on a commit whose workspace version was still 3.0.1 and whose CHANGELOG had no 3.0.2 section, so the release workflow's verify-release job failed. Record the version and move the Unreleased notes under a 3.0.2 heading so the tag can be re-cut on this commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tobyhede
reviewed
Nov 2, 2026
tobyhede
left a comment
tobyhede
left a comment
Contributor
There was a problem hiding this comment.
Review attestation
Reviewed b531a1c · posted from Claude Code · claude-opus-5-5 · effort large
Sources: code-review · claude-opus-5-5
Skills: code-review
Blocking (1)
Cargo.toml:6patch bump for a release with breaking changes; should be3.1.0
Findings (2): 1 major, 1 minor — 2 inline, 0 below.
Generated by Claude Code
The release notes include changes that refuse previously accepted statements and raise the MSRV to 1.89.0, so this is a minor release, not a patch. Publishing it as 3.0.2 would move the floating cipherstash/proxy:3.0 Docker tag onto those changes.
Add the refused reads and the require_tls startup failure to the upgrade list, correct the claim that every listed change is a refusal, warn that the latest Docker tag moves to this release, and date the release for today.
calvinbrewer
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The v3.0.2 release (run 41495739858) failed in
verify-releasebecause the tag was created before a prepare-release PR had landed, so nothing was published.The release notes include changes that refuse previously accepted statements and raise the minimum Rust version to 1.89.0, so this is a minor release rather than a patch.
Publishing it as 3.0.2 would have moved the floating
cipherstash/proxy:3.0Docker tag onto those changes.What
Per the Releasing process:
[workspace.package].versionto3.1.0and refreshCargo.lock.Unreleasednotes under a## [3.1.0] - 2026-11-04heading and add the compare links.ANNOUNCEMENT.mdfor GitHub Discussions.The branch name still says
v3.0.2; that does not affect the release.After merge
No
v3.0.2tag or release exists, so there is nothing to delete.From a clean, up-to-date
main:Then publish
ANNOUNCEMENT.mdto GitHub Discussions and remove the file.If the release slips past 2026-11-04, update the
CHANGELOG.mddate and the changelog link inANNOUNCEMENT.md.🤖 Generated with Claude Code