ci: measure the semver gate against 0.6.1 - #136
Merged
Merged
Conversation
Follow-up to the publish, per docs/RELEASING.md. Until this lands every PR is compared against a release the index no longer serves as newest. Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.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.
Follow-up to the 0.6.1 publish, per
docs/RELEASING.md.baseline-versionmoves 0.6.0 → 0.6.1 now that 0.6.1 is on the index. Left at 0.6.0 the gate compares every PR against a superseded release; moved before the publish it names a version the job cannot fetch.Signed-off-by: Vyncint Ng 115854244+vyncint@users.noreply.github.com