Packages: Add support for publishing stable release of pre-release package #74332
Conversation
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
aduth
added
the
[Type] Project Management
|
Size Change: 0 B Total Size: 3.08 MB ℹ️ View Unchanged
|
tyxla
approved these changes
Jan 2, 2026
Member
tyxla
left a comment
tyxla
left a comment
There was a problem hiding this comment.
Looking good, thanks for following up 👍 🚀
| 'Fifth line', | ||
| ], | ||
| 'patch', | ||
| '0.1.0' |
Member
There was a problem hiding this comment.
Probably overkill, but do we also need a test that "Stable release" promotes to major only if it's currently on < 1.0.0?
Member
Author
There was a problem hiding this comment.
Probably overkill, but do we also need a test that "Stable release" promotes to major only if it's currently on < 1.0.0?
I think it could make sense. In earlier iterations I had been more explicit in documentation that "Stable release" heading would have no effect on stable packages, which would imply it's an expected behavior we should test for.
Updated in fa3bfaf
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Co-authored-by: Marin Atanasov <[email protected]>
This reverts commit 96dbb11.
aduth
force-pushed
the
update/pre-release-stable-publish
branch
from
b72050f to
6a263dc
Compare
|
Flaky tests detected in 6a263dc. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/20751624503
|
ciampo
pushed a commit
that referenced
this pull request
Jan 7, 2026
…ckage (#74332) * Packages: Add support for publishing stable release of pre-release package * Add code syntax highlighting for version specifiers Co-authored-by: Marin Atanasov <[email protected]> * Add test case for no effect on stable versions * TypeScript-ify common bin script * Revert "TypeScript-ify common bin script" This reverts commit 96dbb11. --------- Co-authored-by: Marin Atanasov <[email protected]> Co-authored-by: aduth <[email protected]> Co-authored-by: tyxla <[email protected]>
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.
What?
Follow-up to #74285
Updates the packages publishing workflow script to detect a "stable release" heading in a package changelog to allow a pre-release 0.x package to be bumped to 1.0.0.
Why?
Without these changes, a
<1.0.0package can never become a>=1.0.0package.Testing Instructions
Review included documentation changes for accuracy.
Verify tests pass: