Skip to content

chore(release): prepare 2.3.0-shuv.3 - #499

Merged
shuv1337 merged 2 commits into
integration-v2from
release-shuv3-prep
Nov 16, 2026
Merged

shuv1337 merged 2 commits into
integration-v2from
release-shuv3-prep

Conversation

@shuv1337

Copy link
Copy Markdown
Owner

Outcome

Prepares 2.3.0-shuv.3 on npm channel latest from the current default branch (513994132e905c3fdd8d21fff3f51310e899dc61, the #497 merge). Metadata only: the CLI manifest and the single lockfile workspace version line move 2.3.0-shuv.2 → 2.3.0-shuv.3, and CHANGELOG.md gains the release notes.

  • Base: origin/integration-v2 = 513994132e905c3fdd8d21fff3f51310e899dc61, freshly fetched; git ls-remote --symref origin HEAD still reports refs/heads/integration-v2 as the remote default. The stale parent checkout (72423e0520, with its untracked packages/posts/ and services/www/) was left untouched.
  • Upstream pin stays frozen at 0fad04b3d5a8d5f40e6147573192a7e076787522; this PR adds no upstream sync.
  • The version stays fork-qualified. nextForkVersion takes the base from the checked-in CLI manifest and resolves 2.3.0-shuv.3; a bare 2.3.0 is rejected for latest. The upstream root manifest remains 2.3.0.
  • Delta: 3 files, +41 / −2. No dependency, code, API, generated-client, workflow or release-system change. No feature flag (metadata plus already-merged fixes), no Changeset.

What is actually unreleased since 2.3.0-shuv.2

.2 merged at 27840dc9a8d0d1454b213aeb016ffae893e9420e. Since then:

Every note claim was checked in this head's tree, not only in commit subjects:

Note claim Evidence at this head
UTF-8-safe text and shell cuts packages/util/src/text-boundary.ts (head/tail/utf8Tail), used by packages/core/src/shell.ts page 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.ts
Invalid filename glob is named packages/core/src/tool/plugin/glob.ts (Invalid glob in pattern …), packages/core/src/tool/plugin/grep.ts (Invalid glob in include …)
Server handler-defect 500 is readable packages/server/src/middleware/defect-response.ts (JSON UnknownError with ref, mounted global: true from packages/server/src/routes.ts); that file is byte-identical to the upstream pin
Subagent replayed state from outstanding work packages/core/src/session/execution/subagent-report.ts records the outstanding snapshot; packages/core/src/session/subagent-completion.ts derives state from recovery.outstanding and formats the body at delivery
New-timeline subagent rows packages/session-ui/src/timeline-next/event-row.tsx summarizes background shells only; row.tsx/event-row.tsx render a static status glyph (5d55571d8d removed the spinner)
App extras packages/app/src/servers/connect/pairing.ts carries name; hex detection/tip in desktop and packages/app/src/runtime/i18n/en.ts; script/ast-grep/dialog-size.yml enforces dialog size presets
Updater fix packages/cli/src/services/updater.ts check() resolves the published version first: equal → already installed, owner set → managedMessage(managedError(...)) with the exact command, otherwise available; covered by packages/cli/test/updater-install.test.ts

Claims deliberately not made:

Verification (this checkout; Linux x64; Bun 1.4.4)

Package suites ran under an isolated HOME, XDG roots and TMPDIR. No live service, managed server, provider configuration or package-manager upgrade was touched.

Check Result
bun install --frozen-lockfile 1,597 packages, no lockfile change
Version resolver: OPENCODE_CHANNEL=latest OPENCODE_VERSION=2.3.0-shuv.3, release unset 2.3.0-shuv.3, latest, release=false, preview=false
Version resolver: latest, no explicit version 2.3.0-shuv.3 (from published .2 plus the checked-in minimum)
Version resolver: bare 2.3.0 rejected — Release versions must be <upstream>-shuv.<n>
packages/script bun test 22 pass / 12 skip / 0 fail
packages/cli publish-order + publish-ownership + launcher 10 pass / 0 fail
packages/cli updater-install 33 pass / 4 skip / 0 fail
Root bun run check 40/40 tasks
bun turbo typecheck --force (uncached) 40/40, 0 cached
bun run lint exit 0
git diff --check and Prettier on the changed files clean

The resolver was imported directly (packages/script/src/index.ts), so no publishing module ran; release stays false without OPENCODE_RELEASE.

Platform limits: local execution is Linux x64 only and fork CI has only ubuntu-latest legs. 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.md adds v2.3.0-shuv.3 — 2026-11-15 (Pacific date) in the same shape as .2. .3 is unpublished: public npm latest is 2.3.0-shuv.2 for both shuvcode and shuvcode-node, both .3 endpoints return 404, and there is no v2.3.0-shuv.3 tag or GitHub release.

This PR does not tag, publish, dispatch or install anything. publish.yml creates the tag and GitHub release for the requested version and channel when the release owner dispatches it after a protected merge with green gates.

Set the CLI manifest and lockfile release floor to 2.3.0-shuv.3 and add the maintenance release notes for the upstream sync through 0fad04b (#497) and the #496 updater fix. No code, API or generated surface changes.
A current Volta/mise install now reports up to date; a newer release names the version and command. Wording only.
@shuv1337
shuv1337 merged commit 61f0cb0 into integration-v2 Nov 16, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant