Repository navigation
chore: retire the npm next prerelease channel - #132
Merged
Merged
Conversation
The workflow that published `next` builds was removed, and the remaining script published from a local machine without provenance. Every version under `zerion-cli` is public on npm, so testing builds don't belong there. Drop scripts/publish-next.sh and the README's `@next` section, and point testers at installing a branch straight from GitHub instead. 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
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.
Why
nextbuilds were meant for testing unreleased changes, but npm has no private corner: every version published underzerion-cliis public, installable by anyone, and stays on the registry for good. The README (which is also the npmjs.com page) told people to runnpx zerion-cli@next.The CI workflow that published them was removed earlier. The remaining
scripts/publish-next.shpublishes from a local machine, so those builds have no provenance. Thenexttag currently points at a build older than the latest release.Changes
scripts/publish-next.sh.publish-next.ymlbullet and the "Prerelease channel (@next)" section. A short "Testing unreleased changes" section now points tonpm install -g github:zeriontech/zerion-ai#<branch>.router.test.mjs: reword a comment that referenced the deleted workflow. The version assertion is unchanged.Testing
npm install -g github:zeriontech/zerion-ai#maininto a throwaway prefix with an empty cache (Node 22.23, npm 10.9) installs cleanly, and bothzerion --versionandzerion-cli --versionprint1.10.0.The
nextdist-tag itself is removed on npm separately by a maintainer (npm dist-tag rm zerion-cli next).🤖 Generated with Claude Code