-
Notifications
You must be signed in to change notification settings - Fork 12
W-19293277: bump version number on next #478
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
Changes from all 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 |
---|---|---|
|
@@ -237,7 +237,7 @@ | |
"The 'versionToTagMappings' section defines the mapping between released tags for our CLI plugin and the org version that each tag supports." | ||
], | ||
"target": { | ||
"versionNumber": "65.0", | ||
"versionNumber": "66.0", | ||
"matchingDevServerVersion": "~13.0.27" | ||
}, | ||
"versionToTagMappings": [ | ||
|
@@ -254,7 +254,7 @@ | |
"tagName": "prerelease" | ||
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. The above need updates too, right? 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. Not yet, after SB0, right? 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. 64.0 is the latest as 256 is the release across all of production. 65.0 > yes, SB0 scheduled for 8/11/2025. So you can do it today, its close enough. |
||
}, | ||
{ | ||
"versionNumber": "65.0", | ||
"versionNumber": "66.0", | ||
"tagName": "next" | ||
} | ||
] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please bump the dependency version and matching devServerVersion in a follow up PR?