[tool] Support promoting to 1.0 in batch releases#12262
Conversation
Adds a new "promote" keyword recognized by the batch release changelog processor, which allows for a pre-1.0 package to be promoted to 1.0 using the usual batch release process.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a promote option to the VersionChange enum, enabling pre-1.0 packages to be promoted to version 1.0.0. It adds validation to ensure promote is only applied to pre-1.0 packages, throwing an error otherwise, and includes corresponding unit tests. Feedback suggests removing redundant setup code in the new tests, as createTestPackage() already creates the pending_changelogs directory and writes the default changelog header.
stuartmorgan-g
added
the
autosubmit
auto-submit
Bot
removed
the
autosubmit
|
autosubmit label was removed for flutter/packages/12262, because - The status or check suite Dashboard Checks has failed. Please fix the issues identified (or deflake) before re-applying this label. |
stuartmorgan-g
added
the
autosubmit
auto-submit
Bot
removed
the
autosubmit
|
autosubmit label was removed for flutter/packages/12262, because - The status or check suite Dashboard Checks has failed. Please fix the issues identified (or deflake) before re-applying this label. |
2 participants
Adds a new "promote" keyword recognized by the batch release changelog processor, which allows for a pre-1.0 package to be promoted to 1.0 using the usual batch release process.