chore(release): check dpp-vocab in the semver gate - #130
Merged
Conversation
Up to standards ✅🟢 Issues
|
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.
dpp-vocabwas excluded fromjust semverbecause it had no crates.io baseline to diff against. It shipped in 0.17.0, so the exclusion is removed and all 11 publishable crates are now checked.Verified: the recipe runs clean across all 11, building a baseline for
dpp-vocabfrom the published 0.17.0. No findings, which is the expected state immediately after a release — current equals published until new work lands.RELEASE.mdnow states the general rule rather than the one-off: a new crate is excluded for its first release and put back afterwards. A crate left excluded is a crate whose public API nobody is checking, which is the silence this gate exists to break.