Merged
Conversation
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.
Which issue does this PR close?
N/A. This PR prepares the v0.56.0 release.
Rationale for this change
The release preparation work had drifted in a few places: version synchronization was incomplete across the core workspace, the release docs referenced the wrong upgrade path, and the changelog plus upgrade notes had not been brought up to date for v0.56.0. This change prepares the release end to end and fixes the tooling gap so future release bumps update the workspace consistently.
What changes are included in this PR?
This updates release-managed versions across core, bindings, and integrations, regenerates dependency manifests, refreshes the v0.56.0 changelog and upgrade notes, and corrects the release documentation checklist. It also fixes
dev/src/release/package.rssojust update-versionsyncs internal workspace package versions and path dependency constraints instead of leaving part of the core workspace behind.Validation used for this release prep:
cargo test --manifest-path dev/Cargo.toml,cargo fmt --check --manifest-path dev/Cargo.toml,cargo metadata --manifest-path core/Cargo.toml --no-deps, andcargo check --manifest-path core/Cargo.toml --workspace.Are there any user-facing changes?
Yes. The v0.56.0 release metadata, changelog, and upgrade documentation are updated, and the release tooling now keeps internal workspace versions in sync during future version bumps.
AI Usage Statement
AI-assisted: GPT-5 was used to help prepare the release changes and documentation updates.