workflow: separate version bumping and publishing on release #6879
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.
Workflow Changes
npm run release
script moved to top-level with an interactive prompt to select the packagenpm run release
instead of GH action dispatchingnpm run release
locally at project root of the latestmain
branchChanges Details
npm run release
moved to root, and no longer runs building and publishing.--skipBuild
option has been removed. We useprepublishOnly
hook to trigger the build before publishing.changelog
scripts in each package has been inlined in the release script to reduce duplicationnpm publish
instead ofyarn publish
since we already handle the version bumping.New Features
npm run release
will show commits between the last release of a package for the maintainer to reference