Packages: Add command to publish to npm targeting WP major release #40927
Conversation
This file contains 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
gziolo
force-pushed
the
update/npm-wp-publishing
branch
from
b82e077 to
e9252a3
Compare
|
Size Change: 0 B Total Size: 1.24 MB ℹ️ View Unchanged
|
gziolo
requested review from
ryanwelcher,
ntwb,
nerrad and
ajitbohra
as code owners
adamziel
reviewed
May 9, 2022
|
|
||
| if ( releaseType === 'wp' ) { | ||
| log( | ||
| '>> Skipping CHANGELOG files processing when targeting WordPress core.' |
adamziel
approved these changes
May 9, 2022
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?
Part of the efforts to automate npm publishing as discussed in #37820.
Adds a new command that automates the process of publishing npm packages targeting the given major WordPress release.
Why?
At the moment the process of publishing to npm changes targeting the current major WordPress release is very manual and repeats every week. We want to automate it with GitHub action that runs behind the scenes the following:
How?
Introduce a new command
npm-wpfor the./bin/plugin/cli.jstool that we have been using for npm publishing for quite some time.Testing Instructions
Ensure that the
--wp-versionoption is mandatory:Ensure that the command runs correctly when the WP version is provided:
Screenshots or screencast
Test run:
I managed to publish npm packages with this action:
I verified that the
@wordpress/[email protected]has the correctdist-tagapplied:wp-6.0.