Packages: Introduce release types to npm publishing script #33329
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
gziolo
added
npm Packages
|
Size Change: -162 B (0%) Total Size: 1.07 MB
ℹ️ View Unchanged
|
gziolo
force-pushed
the
update/npm-publishing-release-types
branch
from
e204f0d to
c497858
Compare
gziolo
requested review from
ajitbohra,
chrisvanpatten,
nerrad and
ntwb
as code owners
12 tasks
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.
Description
This PR introduces a new CLI command for publishing packages to npm for all the bugfixes cherry-picked to
wp/trunkbranch during the WordPress release cycle.How has this been tested?
I haven't fully tested, but the command would be:
./bin/plugin/cli.js npm-bugfixScreenshots
Types of changes
New feature (non-breaking change which adds functionality).