release(release): promote the GitHub Packages publish setup - #18
Merged
Merged
Conversation
…GitHub Packages registry
feat: publish wp-coding-standards to GitHub Packages
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Promotes the GitHub Packages publish setup to
main: the rename to@bemidjistate/wp-coding-standards, the tag-triggered publish workflow (no.npmignoreby design — the tarball matches the git-dep content, committedvendor/included), and the README consumption docs. Merging cuts3.4.5and the tag publishes the package.Verification
PR #17 CI green (tool-binaries verification + PR title);
releasealready containsmain(pre-merged, fast-forward), so this promotion is conflict-free.