Bump workspace version to 0.29.0 - #654
Merged
Merged
Conversation
Prepares the v0.29.0 release. Updates both lockfiles: the root one and crates/wasm-quarto-hub-client/Cargo.lock, which records path-dependency versions in its own workspace.
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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.
Version bump for the v0.29.0 release, per
claude-notes/instructions/release-runbook.mdstep 2.The release workflow's preflight job fails unless the git tag exactly equals
[workspace.package].version, so this has to land onmainbeforev0.29.0is tagged.Changes
Cargo.toml:[workspace.package].version0.28.0 → 0.29.0Cargo.lock:cargo update --workspace(workspace members only; no external dep moved)crates/wasm-quarto-hub-client/Cargo.lock: the second lockfile — that crate declares its own[workspace], so a rootcargo updatedoes not reach it. Missing it leaves unrequested churn for the next person to runcargo xtask verify(the v0.17.0 bump missed it).Verification
cargo build --bin q2 --locked→q2 (quarto 2) 0.29.0. The--lockedbuild is the real gate; CI builds--locked, so both lockfiles must already be in sync.cargo nextest run --workspace→ 13675 passed, 199 skipped, 0 failed.npm run build:wasmfromhub-client/→ succeeds and leaves the tree clean, confirming the second lockfile is right.Scope is whatever is on
mainat merge: 142 commits since v0.28.0. PRs #638 and #452 stay open and are not in this release.