Conversation
The Go CLI is distributed as GitHub release binaries, with go install, as the container image and through the GitHub Action. steadybit@5.0.0 on npm is the last version there; the README tells npm users how to move. CI now checks that the image reports the version stamped into it.
…eleases Go only resolves v2+ tags for a module whose path ends in the major version; with the old path, go install @latest built the latest commit. A binary built that way reports its module version.
achoimet
force-pushed
the
build/drop-npm
branch
from
September 25, 2026 14:28
c129ffa to
69eb133
Compare
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.
The Go CLI is no longer published to npm (decision for v6).
internal/tools/npmpkg, thenpm/launcher) and the npm publish steps are removed, along with the release job'sid-tokenpermission, which only npm provenance used. Releases are now the GitHub release (goreleaser binaries, archives and checksums), the Docker image, and the GitHub Action on top of them.go install, the container image or the Action. A note tells npm users thatsteadybit@5.0.0is the last npm version, and how to switch; profiles keep working.github.com/steadybit/cli/v6. Go only resolves v2+ tags for a module whose path ends in/vN. With the old path,go install github.com/steadybit/cli/cmd/steadybit@latestwould have built the latest commit onmain, not the release.go installreports its module version from the build info, while releases keep the stamped version. CI now checks that the Docker image reports the version it was built with. The post-releaseverify-actionjob already checks the downloaded binaries.Verified locally:
go vetandgo testpass, a goreleaser snapshot reports its version, and a Docker build reports itsVERSIONand passes the container suite (20/20).After v6.0.0 is out (package owner):
npm deprecate steadybit "The Steadybit CLI is now a Go binary: see https://github.com/steadybit/cli#installation". The@steadybit/cli-*packages no longer need to be created.