chore(release): v0.12.0#37
Merged
Merged
Conversation
Learning/debug mode + trust-duration dashboard + P1 security hardening. Schema v9->v10 (learning_events); older binaries refuse a v10 DB.
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
1 participant
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.
Bumps the workspace to 0.12.0 (Cargo.toml + Cargo.lock + CHANGELOG).
This is the release-trigger that was missed: the v0.12.0 bump was pushed to PR #36 after it had already been squash-merged, so the bump never reached
mainandrelease-plznever tagged. The feature/security content from #36 is already onmain; this PR adds only the version bump.On merge:
release-plzreads0.12.0fromCargo.toml, creates+pushes tagv0.12.0, which triggersrelease.ymlto build the arm64 macOS binary and publish the GitHub Release + Homebrew.Pre-merge gates: cargo-deny advisories ok; secret scan clean; workspace at 0.12.0.