-
Notifications
You must be signed in to change notification settings - Fork 639
[rush] Add support for premajor and prepatch bump types #4994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
{ | ||
"changes": [ | ||
{ | ||
"packageName": "@microsoft/rush", | ||
"comment": "Add support for premajor and prepatch bump types", | ||
"type": "none" | ||
} | ||
], | ||
"packageName": "@microsoft/rush" | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,8 +25,6 @@ import { cloneDeep } from '../utilities/objectUtilities'; | |
* This is a copy of the semver ReleaseType enum, but with the `none` value added and | ||
* the `premajor` and `prepatch` omitted. | ||
* See {@link LockStepVersionPolicy._getReleaseType}. | ||
* | ||
* TODO: Consider supporting `premajor` and `prepatch` in the future. | ||
*/ | ||
export enum BumpType { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do the numeric values of these need to be updated to reflect the order of increasing severity? These may be used to ensure that the most severe bump type wins if multiple are specified in a package's changefiles. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. However, we need to confirm that doing that as a breaking API change won't cause issues. Maybe we make There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @iclanton IMHO it makes sense for them to be ordered in more natural way, but as you mentioned it could be a breaking API change. I'll wait for other maintainers to comment on this before making changes here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @octogonz - thoughts? |
||
// No version bump | ||
|
@@ -40,7 +38,11 @@ export enum BumpType { | |
// Minor version bump | ||
'minor' = 4, | ||
// Major version bump | ||
'major' = 5 | ||
'major' = 5, | ||
// Premajor version bump | ||
'premajor' = 6, | ||
// Prepatch version bump | ||
'prepatch' = 7 | ||
} | ||
|
||
/** | ||
|
Uh oh!
There was an error while loading. Please reload this page.