Repository navigation
Bump version to 0.2.0 - #6
Merged
Merged
Conversation
Update the pinned installer download examples in the README to the version being released. 0.2.0 carries the explicit recipient authorization model: gitveil recipient add/remove are the only entry points that change who can decrypt, and seal/resolve fail closed on recipient drift instead of silently consuming it.
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.
Summary
Prepares the v0.2.0 release per
docs/releasing.md:Cargo.toml/Cargo.lock: version 0.1.0 -> 0.2.0.v0.2.0(valid once the release is published).0.2.0 is a minor bump carrying the explicit recipient authorization model (#5):
gitveil recipient add/removeare the only authorization entry points, data commands fail closed on recipient drift, andresolvenever extends access. Breaking relative to 0.1.0: hand-editing the manifest and runningsealno longer performs rewrap or rotation.Because this PR touches
Cargo.toml/Cargo.lock, the release workflow pull-request path also builds all four native target archives as a pre-release rehearsal.After merge
Then approve the
releaseenvironment in Actions, verify the draft assets (SHA256SUMSand attestations), and publish the draft through the GitHub Releases interface.