chore(release): bring the workspace to 0.4.10 so the vta-sdk 0.38 move can publish - #53
Merged
Merged
Conversation
…e can publish Two manifest lines plus the lockfile; all three crates take it through version.workspace = true. No dependency or source changes. The tree has been on 0.4.9 since that tag, and crates.io already holds all three crates at 0.4.9, so tagging again would publish nothing: publish.yml skips any crate already on crates.io at the workspace version, which is the resumability its header describes. A bump is what lets the nine commits since v0.4.9 reach consumers, and the one that matters downstream is the vta-sdk 0.36 -> 0.38 move in #51. Until it publishes, OpenVTC's graph carries a second vta-sdk (0.36.0) and a second didwebvh-rs (0.6.1), each held solely by did-git-sign 0.4.9; both disappear when its floor moves to this release. Signed-off-by: Glenn Gore <glenn.g@affinidi.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
Workspace version 0.4.9 → 0.4.10. Two lines plus the lockfile; all three crates take it through
version.workspace = true. No dependency or source changes.Why a bump rather than re-tagging 0.4.9
The tree has been on 0.4.9 since
v0.4.9was cut, and crates.io already holdsvgi-core,verify-trustanddid-git-signat 0.4.9. Tagging again would publish nothing:publish.ymlskips any crate already on crates.io at the workspace version — the resumability its header comment describes. So the nine commits since that tag cannot reach consumers without a bump.What it releases
Everything on
mainsincev0.4.9, and one change matters downstream:vta-sdk0.36 → 0.38, which also droppeddidwebvh-rs0.6.1 from this graph.did:webvhpublic-host resolution policy and the commit-parser differential.randat 0.8 in Dependabot while rPGP needs it.Why it is wanted now
OpenVTC has moved onto the published VTI releases and is on
vta-sdk0.38.did-git-sign0.4.9 requires^0.36, and it is the only crate there still pulling an older sdk — so OpenVTC's graph carries a secondvta-sdk(0.36.0) and, hanging off it, a seconddidwebvh-rs(0.6.1). They are one obligation wearing two names, and both disappear the moment its floor can move to this release. Nothing is broken meanwhile: no sdk type crosses thedid_git_sign::{config, init}boundary OpenVTC uses.Verification
cargo fmt --all -- --checkclean,cargo clippy --workspace --all-targets -- -D warningssilent, 158 tests passing. The lockfile diff is three lines — the three workspace crates — and nothing else moved.After merge
Push the
v0.4.10tag, which firespublish.yml(crates.io, in dependency order) andrelease.yml(prebuiltverify-trustbinaries). Perpublish.yml's header the tag push has to come from a human or PAT, since aGITHUB_TOKEN-created release cannot cascade-trigger the publish workflow — so that step is yours rather than something I can do.