Bump workspace version to 0.30.0 - #665
Merged
Merged
Conversation
Release runbook step 2: the release workflow's preflight job requires the git tag to equal [workspace.package].version, so the bump lands on main before v0.30.0 is tagged. - Cargo.toml: 0.29.0 -> 0.30.0 - Cargo.lock: cargo update --workspace (workspace members only) - crates/wasm-quarto-hub-client/Cargo.lock: the second lockfile Verified: cargo build --bin q2 --locked prints "q2 (quarto 2) 0.30.0"; cargo nextest run --workspace: 13798 passed, 199 skipped; npm run build:wasm leaves the tree clean. No snapshot changes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0112cioipQzGf118XbJwg7L1
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
2 participants
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.30.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.30.0is tagged.Changes
Cargo.toml:[workspace.package].version0.29.0 → 0.30.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.Verification
cargo build --bin q2 --locked→q2 (quarto 2) 0.30.0.cargo nextest run --workspace→ 13798 passed (1 leaky), 199 skipped, 0 failed.npm run build:wasmfromhub-client/→ succeeds and leaves the tree clean, confirming the second lockfile is right.jsr:@quarto/api/jsr:@quarto/typesare not yet published (jsr.io returns 404).Scope is whatever is on
mainat merge: 11 first-parent commits since v0.29.0 (PRs #661, #662, #663 plus direct commits). PR #664 stays open and is not in this release.🤖 Generated with Claude Code
https://claude.ai/code/session_0112cioipQzGf118XbJwg7L1