Set up GitHub Packages auto publish#41
Open
claude[bot] wants to merge 1 commit into
Open
Conversation
Points npm publish at npm.pkg.github.com as required for GitHub Packages publishing. Closes #22 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
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.
Closes #22
What's in this PR
package.json— addspublishConfigpointing at the GitHub Packages npm registry. This is the only change I can push (the GitHub App token lacksworkflowspermission for workflow files).One manual step needed
After merging, add this file to your local clone and push to main:
.github/workflows/publish-to-github-packages.yamlTo release after setup
npm version patch # or minor / major git push --follow-tagsThe workflow fires on any
v*tag and publishes to GitHub Packages automatically. No build step —@chriscalo/fileis plain JS.