Repository navigation
ci(npm): mirror vaultx-cli 1.0.0 to GitHub Packages - #1
Merged
Merged
Conversation
GitHub Packages only accepts account-scoped npm names, so the npmjs release is republished as @dijo-404/vaultx-cli. The manual workflow verifies the npmjs tarball against a pinned SHA-256, changes only the name field (asserted), publishes with the workflow token so the package is linked to this repository, then reads it back, installs it fresh, runs the launcher end to end, and asserts the repository association. Co-Authored-By: Claude Opus 5.5 <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.
Summary
Adds a manual
publish-github-packagesworkflow that mirrors the npmjsvaultx-cli@1.0.0release to GitHub Packages as@dijo-404/vaultx-cli, linked to this repository. Also adds an install note to the README.GitHub Packages' npm registry only accepts account-scoped names, so the package is renamed. That is the only change: the job asserts every other
package.jsonfield matches, and all other files are the npmjs bytes.What the job checks
namediffers from the npmjspackage.json.GITHUB_TOKEN(packages: write), which links the package to this repo. If the version already exists, it verifies instead of republishing.--ignore-scriptsrunsvaultx --version, which exercises the on-demand release download and SHA-256 check.Dijo-404/vaultx-cli.This follows the same pattern as the
monolith-climirror.🤖 Generated with Claude Code