Documentation: Update the workflow for npm publishing #42189
Merged
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
[Type] Developer Documentation
gziolo
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
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?
Related to Making the Tech Editor Release Lead Role More Creative and Less Repetitive.
As part of the effort to simplify the process of backporting changes from the Gutenberg plugin to WordPress major release, we also integrated npm publishing with the GitHub UI.
Why?
The process for publishing npm package is now simplified with GitHub actions and it should be reflected in the existing documentation.
How?
I included all missing details on how to trigger npm publishing for different types:
The updated document can be previewed at:
https://github.com/WordPress/gutenberg/blob/1bd1dcf0e58d1a1a7d64606193ded053519d881a/docs/contributors/code/release.md
Images won't be visible in the preview until we merge changes to the
trunk.