chore(release): bump version to 3.3.0#96
Open
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
Open
Conversation
Bump 3.2.0 -> 3.3.0 (minor) for the inline OpenVEX feature already staged under CHANGELOG `## [Unreleased]`. Synced via scripts/version-sync.sh across Cargo.toml (workspace version + core dep pin), Cargo.lock, all npm packages (main + platform shims + lockfile), and pypi/pyproject.toml. The Release workflow reads this version from Cargo.toml; once merged it can be dispatched to publish v3.3.0 and roll the CHANGELOG over. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Bumps the workspace version 3.2.0 → 3.3.0 (a minor bump) so the new inline OpenVEX generation on
apply/scan(--vex <path>) feature — already staged under## [Unreleased]inCHANGELOG.md— can be released.There's no automatic version computation in this repo: the
Releaseworkflow only reads the version fromCargo.toml, so the bump has to land onmainfirst.Changes
Generated via
scripts/version-sync.sh 3.3.0(+Cargo.lockupdate):Cargo.toml—[workspace.package] versionand the=3.3.0socket-patch-coredep pinCargo.lock—socket-patch-cli/socket-patch-corepackage-lock.jsonpypi/socket-patch/pyproject.tomlNo source/behavior changes — version strings only.
Release steps (after merge)
3.3.0, confirms nov3.3.0tag exists, and that## [Unreleased]is non-empty.rollover-changelog.shstamps## [Unreleased]→## [3.3.0] — <date>automatically.🤖 Generated with Claude Code