chore(release): cut 0.1.0 - #1062
Merged
Merged
Conversation
The first STABLE release: signed, notarized, and published as `releases/latest` rather than as a prerelease. Around sixty pull requests separate it from the 0.0.2-beta.1 prerelease. `package.json` and `package-lock.json` move to 0.1.0, which is what the release workflow validates the channel against: `CHANNEL=stable scripts/release/identity.mjs` now resolves `tag=v0.1.0 / prerelease=false / make_latest=true`, and the prerelease channel correctly REFUSES a stable version. The notes are the draft from the release-readiness ledger with every PENDING marker resolved — each of those PRs is merged — plus the four fixes that landed after it was written (#1057 interrupted streams, #1058 detached tmux shells, #1060 the paste envelope, and the tier-0 install consent in #1049). The landing page needs no change and is not touched here: it resolves `releases/latest`, which GitHub defines as the newest release that is neither a draft nor a prerelease, so the rolling nightly can never win it. That endpoint 404s today because no such release exists, which is exactly why the download buttons fall back to the Releases page and the status line is silent. Publishing this flips both. Co-Authored-By: Claude Opus 5 (1M context) <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.
The first stable Agent Code release — signed, notarized, and published as
releases/latestrather than as a prerelease. Around sixty pull requests separate it from the0.0.2-beta.1prerelease.What is in here
package.json+package-lock.json→ 0.1.0.docs/decomposition/release-0.1.0-notes.md, finalized: everyPENDINGmarker from the ledger draft resolved (each of those PRs is merged), plus the four fixes that landed after it was written — fix(claude): seal an Esc-severed stream, and keep a sleep a sleep (#1040) #1057 (interrupted streams), fix(tmux): reap a closed terminal's shell once its undo window has passed #1058 (detached tmux shells), fix(claude): show the user's words, not Claude's paste envelope #1060 (the paste envelope), and the tier-0 install consent in fix(security): approval surfaces show reordering and invisible characters as escapes #1049.Why 0.1.0 specifically
The release workflow validates the channel against the version (
scripts/release/identity.mjs, added in #1035). Dry-run on this branch:Both directions behave: a stable release of a prerelease version would make a beta
latest, and a prerelease of a stable version would burn the stable tag.The landing page is deliberately untouched
It already resolves
releases/latest, which GitHub defines as the newest release that is neither a draft nor a prerelease — so the rolling nightly can never win it. That endpoint 404s today, which is exactly why the download buttons fall back to the Releases page and the status line is silent. Publishing this flips both automatically:findDiskImagesuffix-matches-arm64.dmg/-x64.dmg, and the real beta assets are namedAgent.Code-0.0.2-beta.1-arm64.dmg, soAgent.Code-0.1.0-arm64.dmgmatches.After merge
Dispatch
release.ymlwithchannel=stable,publish_release=true, both tag/name inputs left empty (they derive frompackage.json).Still open and not blocking, recorded in the ledger: a replacement hero screenshot and the Cloudflare Pages connect + domain are owner items; README screenshots predate Nord.
🤖 Generated with Claude Code