v0.1: npm publish prep + release workflow#1
Closed
protosphinx wants to merge 1 commit into
Closed
Conversation
Member
Author
|
Superseded: v0.5 npm publish workflow + CHANGELOG already shipped on main. |
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.
Scope
Prepares
skillcheckfor npm publishing by adding a GitHub Actions release workflow, aCHANGELOG.mdseeded with the v0.0 entry, and an.npmignoreto keep the published tarball lean.Checklist
.npmignoreexclusions: runnpm pack --dry-runand inspect the file listNPM_TOKENsecret in repo Settings → Secrets and variables → ActionsCHANGELOG.md: move items from[Unreleased]→[0.1.0]and add the release date.github/workflows/release.yml— add provenance/attestation steps if desiredv0.1.0) to trigger the release workflowRoadmap context
See the Roadmap section of the README.
Generated by Claude Code