chore: track npm CLI beta 0.0.10 release - #75
Closed
jiashuoz wants to merge 1 commit into
Closed
Conversation
Carry the published v0.0.10 CLI archives into the npm wrapper with no runtime change. The wrapper source is byte-identical to 0.0.9's; only the pinned version, the four archive hashes, and the four binary hashes move. v0.0.10 is the first release carrying the hosted v0 command surface (#70). `rainier diff` is gone from the CLI in it, which no published binary had yet: v0.0.9 was tagged 2026-09-09T03:15Z and #70 merged at 18:05Z the same day, so every installed wrapper still served a command the contract removed. The server route `GET /v0/sessions/{id}/diff` is untouched, per contract §2.3. Verified: `make verify` green (tests, build, vet); `go test ./cmd/rainier/` including TestDiffIsGone, TestRootHelpInventory and TestHelpAllDocumentsWhatTheDefaultHides; 11/11 npm tests against the new manifest; `npm pack --dry-run` carries exactly the six allowlisted files with no dependencies and no lifecycle scripts. The built darwin/arm64 binary reports `rainier v0.0.10`, refuses `diff` as an unknown command, and its default help is 23 lines. No Go source, backend, or cloud implementation changed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SDSieWT6mnHB1EYXUyz7H
Member
Author
|
Superseded by the automated release workflow (#76). That workflow generates this same manifest from the artifacts it uploads and opens its own pins PR, so merging this one as well would leave two PRs editing the same five files. These hashes are also about to stop being correct: the workflow rebuilds the archives on Linux with the Go version from go.mod and deterministic tar metadata, and clobbers the release assets. The pins recorded here describe the macOS-built assets that are on the release right now, not the ones that will be there afterwards. Closing rather than merging. Its content is preserved in v0.0.10's release history. |
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.
Carries the published v0.0.10 CLI archives into the npm wrapper. No runtime change: the wrapper source is byte-identical to 0.0.9's, and only the pinned version, four archive hashes, and four binary hashes move.
Why now
v0.0.10 is the first published binary carrying the hosted v0 command surface (#70).
rainier diffis gone from the CLI in it, and no released binary had that yet — v0.0.9 was tagged2026-09-09T03:15Zand #70 merged at18:05Zthe same day. Until this publishes, everynpm installstill serves a command the contract removed. The server routeGET /v0/sessions/{id}/diffis untouched, per contract §2.3.Scope
CLI only. Each release archive contains one file, the
rainierbinary. Session-image changes in the same source tag are not delivered by this package and roll out separately; the release notes say so explicitly.Verification
make verifygreen: tests,scripts/build.sh,go vet.go test ./cmd/rainier/includingTestDiffIsGone,TestRootHelpInventory, andTestHelpAllDocumentsWhatTheDefaultHides.npm pack --dry-run: exactly the six allowlisted files, no dependencies, no lifecycle scripts.--ignore-scriptsinto a cleanHOME, then run with an empty cache: it downloaded the real archive, passed both checksum gates, reportedrainier v0.0.10, and refuseddiffas an unknown command.No Go source, backend, or cloud implementation changed.
🤖 Generated with Claude Code
https://claude.ai/code/session_019SDSieWT6mnHB1EYXUyz7H