Merged
Conversation
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.
This adds a complete npm publish pipeline for
sklt, including automatic publishes from GitHub releases, manual publishes from an explicit ref, and dry-run verification paths for both CI and local development.The repository already built a Node-compatible CLI bundle, but publishing still depended on manual
npm publishexecution and there was no repeatable way to validate the package payload before release. That also made it easy for packaging drift to slip past CI. In addition, the npm-facing command and package naming needed to be simplified toskltsonpx skltworks directly.This change renames the npm package and bin to
sklt, updates help text and docs to match, adds a dedicatednpm Publishworkflow with release and manual-dispatch triggers, and introduces a reusablemise run npm-publish-dry-runtask. CI now exercises that dry run so package publication is validated continuously, while the publish workflow skips already-published versions and supports manual dry-run execution with a safe fallback dist-tag.Validation:
mise run npm-publish-dry-runmise run ci