chore(release): bring the workspace to 0.4.11 so the vta-sdk 0.39 move can publish - #56
Merged
Merged
Conversation
…e can publish #55 took `vta-sdk 0.39`; this is the release that makes it consumable. OpenVTC is the reason. It consumes `did-git-sign`, so while the published 0.4.10 declares `vta-sdk ^0.38`, OpenVTC raising its own pin to 0.39 resolves **two** sdk copies — the state its manifest records having escaped for the first time since 0.35, after this obligation had blocked six consecutive minors. Publishing 0.4.11 is what lets that stay one copy. No source change since #55, which itself needed none: neither breaking change in vta-sdk 0.39 (`verify_trust_task_proof_with` becoming generic, `KeyType` gaining ML-DSA variants) touches this workspace. 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.
#55 took
vta-sdk 0.39; this is the release that makes it consumable.OpenVTC is the reason. It consumes
did-git-sign, so while the published 0.4.10 declaresvta-sdk ^0.38, OpenVTC raising its own pin to 0.39 resolves two sdk copies — the state its manifest records having escaped for the first time since 0.35, after this obligation had blocked six consecutive minors (0.23, 0.25, 0.27, 0.31, 0.32, 0.34).Publishing 0.4.11 is what lets that stay one copy.
No source change since #55, which itself needed none: neither breaking change in vta-sdk 0.39 —
verify_trust_task_proof_withbecoming generic over the payload, andKeyTypegaining ML-DSA variants — touches this workspace.Same footprint as the 0.4.10 release (#53):
Cargo.toml+Cargo.lock, nothing else. Tagv0.4.11follows the merge, which is what triggers publish.yml.