Bump main to 1.5.0 for development - #34
Merged
Merged
Conversation
Advances main to the next in-development version after cutting release/1.4.0. The cut_release lane's direct push to main was rejected by branch protection (PR + Unit Tests required), so this does it via PR. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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.
Changes
Advance
main'sMARKETING_VERSIONfrom 1.4.0 → 1.5.0.Why
After cutting
release/1.4.0,mainmust advance to the next in-development version so it never sits on a released version. Thecut_releasefastlane lane tried to do this with a direct push, which was rejected by themainbranch ruleset ("Changes must be made through a pull request" + required "Unit Tests" check). This PR performs that same bump through the required PR flow.Notes
release/1.4.0was created successfully by the cut; only the main-advance step needs this PR.cut_releaselane to open a PR for the main bump instead of pushing directly, so the automation matches branch protection.