[ci] Update prerelease workflows to allow publishing specific packages #33525
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
It may be useful at times to publish only specific packages as an experimental tag. For example, if we need to cherry pick some fixes for an old release, we can first do so by creating that as an experimental release just for that package to allow for quick testing by downstream projects. Similar to .github/workflows/runtime_releases_from_npm_manual.yml I added three options (`dry`, `only_packages`, `skip_packages`) to `runtime_prereleases.yml` which both the manual and nightly workflows reuse. I also added a discord notification when the manual workflow is run.
poteto
changed the title
github-actions
bot
added
the
React Core Team
|
Comparing: 12bc60f...6be4d33 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
yungsters
reviewed
Jun 13, 2025
Comment on lines
+80
to
+97
| - if: '${{ inputs.only_packages }}' | ||
| name: 'Publish ${{ inputs.only_packages }}' | ||
| run: | | ||
| scripts/release/publish.js \ | ||
| --ci \ | ||
| --skipTests \ | ||
| --tags=${{ inputs.dist_tag }} \ | ||
| --onlyPackages=${{ inputs.only_packages }} ${{ (inputs.dry && '') || '\'}} | ||
| ${{ inputs.dry && '--dry'}} | ||
| - if: '${{ inputs.skip_packages }}' | ||
| name: 'Publish all packages EXCEPT ${{ inputs.skip_packages }}' | ||
| run: | | ||
| scripts/release/publish.js \ | ||
| --ci \ | ||
| --skipTests \ | ||
| --tags=${{ inputs.dist_tag }} \ | ||
| --skipPackages=${{ inputs.skip_packages }} ${{ (inputs.dry && '') || '\'}} | ||
| ${{ inputs.dry && '--dry'}} |
There was a problem hiding this comment.
Should we error if both are supplied? (The way this is implemented, they are conflicting.)
There was a problem hiding this comment.
I check it here because yml is such a pain 💀:
react/scripts/release/publish.js
Lines 34 to 39 in 12bc60f
There was a problem hiding this comment.
Ahh, okay! Thanks for clarifying.
yungsters
approved these changes
Jun 13, 2025
1 task
17 tasks
poteto
pushed a commit
that referenced
this pull request
Jun 23, 2025
## Summary Follow-up to #33525 Fixes `Unsupported tag: "false"` (https://github.com/facebook/react/actions/runs/15773778995/job/44463562733#step:13:12) which also affects nightly releases. ## How did you test this change? - [x] Run successful, manual prerelease from this branch: https://github.com/facebook/react/actions/runs/15774083406
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.
It may be useful at times to publish only specific packages as an experimental tag. For example, if we need to cherry pick some fixes for an old release, we can first do so by creating that as an experimental release just for that package to allow for quick testing by downstream projects.
Similar to .github/workflows/runtime_releases_from_npm_manual.yml I added three options (
dry,only_packages,skip_packages) toruntime_prereleases.ymlwhich both the manual and nightly workflows reuse. I also added a discord notification when the manual workflow is run.