Repository navigation
chore(release): prepare 2.3.0-shuv.2 - #495
Merged
Merged
Conversation
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.
Summary
Small, separate release-prep PR for
2.3.0-shuv.2on npmlatest, based on freshly fetchedorigin/integration-v2617bc15ee9663272ec0a1121334d65abbd79abef(merge of #494; verified as an ancestor).Metadata only — no code, API, generated client, protocol or OpenAPI surface changes:
packages/cli/package.jsonversion2.3.0-shuv.1→2.3.0-shuv.2(checked-in release floor)bun.lockshuvcodeversion2.3.0-shuv.1→2.3.0-shuv.2CHANGELOG.mdv2.3.0-shuv.2maintenance notes above the existing fork notesbun.lockdiff in full: the single"version"line underpackages/cli. Root manifest stays upstream2.3.0; nothing bare-upstream can be published. No feature flag: the flags were made irrelevant by upstream's own shell-timeout graduation and a release-prep commit adds no behavior to gate.Fork identity/hiding/dependency invariants are untouched by this diff (Shuvcode name/bin/XDG/ports, npm-only updates and guarded publish, hidden Claude Agent SDK provider, managed-policy waits). The #490/#491/#492 CI/test fixes are already in the base.
Release notes added
The timeout wording was read from
packages/core/src/tool/plugin/shell.tsand its tests (treats a foreground timeout of zero as the default timeout,stops a background command when its explicit timeout expires), not inferred. #493 (PowerShell first-test stall) is not claimed fixed; this branch carries only the existing diagnostics.Validation (this head)
OPENCODE_CHANNEL=latest bun -e 'await import("./packages/script/src/index.ts")')channel: latest,version: 2.3.0-shuv.2; npmlatestread as2.3.0-shuv.1for bothshuvcodeandshuvcode-nodebun install --frozen-lockfilepackages/scriptbun test(version + pack + highlights)packages/clipublish-order,publish-ownership,updater-install,launcherbun run checkshuvcodeuncached from the manifest bump)git diff --check/ Prettier--checkCross-platform: local evidence is Linux x64 only. This repo's
unitande2ejobs (the effective release gates) run onubuntu-latestonly, andpublish.ymlbuilds the Linux/macOS/Windows Bun and Node packages onubuntu-latestfor the release artifacts — that pipeline, not this host, covers the other targets. No Windows/macOS execution is claimed here. The base head already had a green full sync CI run (unit+e2e43567537752,typecheck43567537749), but this release-prep head needs its own greenunit+e2e; thechore(release)title enables both.Release run recipe (not dispatched here)
publish.ymlsupports exactly twoworkflow_dispatchinputs:version(required string) andchannel(optional string, defaultlatest). Dispatch on branchintegration-v2at the merge commit:That run gates on
typecheck+test(unit/e2e), builds Bun and Node CLI distributions plus the fivegpt-live-hosthelpers, publishesshuvcode,shuvcode-nodeand their platform packages to dist-taglatestvia theshuv1337/shuvcode-guardedpackages/cli/script/publish.ts, then creates the GitHub releasev2.3.0-shuv.2(non-prerelease because the channel islatest) at$GITHUB_SHAwith the archives and helper assets. The tag is created bygh release create --target $GITHUB_SHA; no separate tag step.Caveats
opencode_shuvcodeguard applies before any restart.### Visualsection: this ischore(release)metadata only with no user-facing UI change, so the repo'sfeat/fix/perfanimated-SVG requirement does not apply.