Repository navigation
chore(release): prepare 2.3.0-shuv.3 - #499
Merged
Merged
Conversation
A current Volta/mise install now reports up to date; a newer release names the version and command. Wording only.
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.
Outcome
Prepares
2.3.0-shuv.3on npm channellatestfrom the current default branch (513994132e905c3fdd8d21fff3f51310e899dc61, the #497 merge). Metadata only: the CLI manifest and the single lockfile workspace version line move2.3.0-shuv.2→2.3.0-shuv.3, andCHANGELOG.mdgains the release notes.origin/integration-v2=513994132e905c3fdd8d21fff3f51310e899dc61, freshly fetched;git ls-remote --symref origin HEADstill reportsrefs/heads/integration-v2as the remote default. The stale parent checkout (72423e0520, with its untrackedpackages/posts/andservices/www/) was left untouched.0fad04b3d5a8d5f40e6147573192a7e076787522; this PR adds no upstream sync.nextForkVersiontakes the base from the checked-in CLI manifest and resolves2.3.0-shuv.3; a bare2.3.0is rejected forlatest. The upstream root manifest remains2.3.0.What is actually unreleased since
2.3.0-shuv.2.2merged at27840dc9a8d0d1454b213aeb016ffae893e9420e. Since then:730296522672c4c1a0abe52d01045a622977b819, fix534ff56692): the update check for Volta- and mise-owned installs.513994132e905c3fdd8d21fff3f51310e899dc61): 22 upstream commitscbe71595e1..0fad04b3d5.Every note claim was checked in this head's tree, not only in commit subjects:
packages/util/src/text-boundary.ts(head/tail/utf8Tail), used bypackages/core/src/shell.tspage windows,packages/session-ui/src/tools/shell-output-machine.ts,packages/tui/src/component/dialog-shell-output.tsx,packages/tui/src/routes/session/index.tsx,packages/core/src/tool/read-filesystem.ts,packages/core/src/ripgrep.ts,packages/core/src/session/title.tspackages/core/src/tool/plugin/glob.ts(Invalid glob in pattern …),packages/core/src/tool/plugin/grep.ts(Invalid glob in include …)packages/server/src/middleware/defect-response.ts(JSONUnknownErrorwithref, mountedglobal: truefrompackages/server/src/routes.ts); that file is byte-identical to the upstream pinpackages/core/src/session/execution/subagent-report.tsrecords the outstanding snapshot;packages/core/src/session/subagent-completion.tsderivesstatefromrecovery.outstandingand formats the body at deliverypackages/session-ui/src/timeline-next/event-row.tsxsummarizes background shells only;row.tsx/event-row.tsxrender a static status glyph (5d55571d8dremoved the spinner)packages/app/src/servers/connect/pairing.tscarriesname; hex detection/tip in desktop andpackages/app/src/runtime/i18n/en.ts;script/ast-grep/dialog-size.ymlenforces dialog size presetspackages/cli/src/services/updater.tscheck()resolves the published version first: equal → already installed, owner set →managedMessage(managedError(...))with the exact command, otherwise available; covered bypackages/cli/test/updater-install.test.tsClaims deliberately not made:
ref, transport and reconnect handling were reverted before chore(sync): merge upstream dev through 0fad04b3d5 #497 landed; the final tree is the plain upstream sync plus audit wording. The generated public client still cancels and ignores an undeclared 500 body and throwsUnexpectedStatus, so it shows a generic failure. That is tracked in feat(client): expose readable server 500 details (upstream candidate) #498 as an upstream candidate, not part of this release, and the changelog says so.Verification (this checkout; Linux x64; Bun 1.4.4)
Package suites ran under an isolated
HOME, XDG roots andTMPDIR. No live service, managed server, provider configuration or package-manager upgrade was touched.bun install --frozen-lockfileOPENCODE_CHANNEL=latest OPENCODE_VERSION=2.3.0-shuv.3, release unset2.3.0-shuv.3,latest,release=false,preview=falselatest, no explicit version2.3.0-shuv.3(from published.2plus the checked-in minimum)2.3.0Release versions must be <upstream>-shuv.<n>packages/scriptbun testpackages/clipublish-order + publish-ownership + launcherpackages/cliupdater-installbun run checkbun turbo typecheck --force(uncached)bun run lintgit diff --checkand Prettier on the changed filesThe resolver was imported directly (
packages/script/src/index.ts), so no publishing module ran;releasestays false withoutOPENCODE_RELEASE.Platform limits: local execution is Linux x64 only and fork CI has only
ubuntu-latestlegs. The changed hex detector keeps Windows and macOS branches that unit tests exercise with simulated platform inputs; that is not runtime proof on those OSes, and none is claimed. The publish pipeline builds the macOS and Windows artifacts by cross-compilation.Release notes and next step
CHANGELOG.mdaddsv2.3.0-shuv.3 — 2026-11-15(Pacific date) in the same shape as.2..3is unpublished: public npmlatestis2.3.0-shuv.2for bothshuvcodeandshuvcode-node, both.3endpoints return 404, and there is nov2.3.0-shuv.3tag or GitHub release.This PR does not tag, publish, dispatch or install anything.
publish.ymlcreates the tag and GitHub release for the requested version and channel when the release owner dispatches it after a protected merge with green gates.