Repository navigation
Move master to the next major - #270
Merged
Merged
Conversation
Releases come from release branches, and master builds the next major that hasn't been branched yet. Set MinVerMinimumMajorMinor to 5.0.
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.
Sets
MinVerMinimumMajorMinorto5.0, somasterbuilds5.0.0-alpha.0.<height>, as described inRELEASING.md(#268).Merging this means the next release from
masteris the start of 5.0. Since 4.2.0,masteronly has dependency updates and repository tooling, so nothing is left out of 4.x. A future 4.x release would branch from the4.2.0tag, because there is norelease-4.xbranch yet.