Sync the workspace version to v0.29.1 - #256
Open
bkearns wants to merge 1 commit into
Open
Conversation
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.
v0.29.1was tagged, and the workspace version was never synced to it.promote-releasepushed this branch and did not open a PR for it — which is precisely the failure the "Workspace version is in step with the latest release tag" check exists to catch:This currently fails Format & Lint on every open PR, because the check runs against the workspace version rather than the diff. Nothing else can merge until it lands.
No hand-editing here — this is the branch the release process already prepared, opened as-is. It bumps
Cargo.tomlto0.29.1and updatesCargo.lockto match, and it is level withmain.Opened while unblocking #255; the branch and its contents are not mine.