Repository navigation
ci: version bump after 7.0 release branch - #231
Merged
Merged
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
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.
GitHub Issue (If applicable): Related to #230
PR Type
What is the current behavior?
mainis on7.0-dev.{height}.release/stable/7.0was cut frommainat 7bffd8a (fix(skills): check the 7.0 line against what Uno.Sdk 7.0.5 pins #230) withnbgv prepare-release, like the 1.1 cut (ci: version bump after 1.1 release branch #152).What is the new behavior?
mainmoves to7.1-dev.{height}, the next Uno.Sdk minor. These are the commitsnbgv prepare-release --commit-message-pattern "ci: Set version to '{0}'"makes onmain.Merge with "Create a merge commit" (not squash or rebase), so
mainkeeps the release branch's version commit in its history.🤖 Generated with Claude Code