chore(release): prepare 1.12.0 - #166
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Yoonwoo-Ha
force-pushed
the
chore/release-1.12.0
branch
from
September 21, 2026 04:17
1f41e3e to
6731167
Compare
Yoonwoo-Ha
added a commit
that referenced
this pull request
Sep 21, 2026
## Summary - distinguish BRE-only escapes such as `grep '\(a\|b\)'` from ordinary inline math while allowing units such as `speed \(v\)/s` - memoize Markdown normalization and consolidate the external spawn CLI type onto the shared contract - tag full-access tmux sessions, propagate the tag through discovery, and retain a visible sidebar warning badge - add the server-authoritative `CHATMUX_DISABLE_FULL_ACCESS=1` kill switch to capability discovery and spawn enforcement - document the deployment control and persistent warning behavior in the provider guide and localized READMEs Follow-up to #165, based on the `1.12.0` main from #166. ## Verification - `npm run verify` on `1.12.0` - Rust: 29 passed - server: 1,863 passed - real tmux/PTY: 50 passed - client: 746 passed - lint, identity check, and production builds passed --------- Co-authored-by: YoonwooHa <he0653@g.skku.edu>
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
2 participants
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
Prepares the v1.12.0 minor release from current main.
Release contents since v1.11.1
This is a minor bump, not a patch: #165 adds a user-facing capability (the per-session Full access option for newly launched local CLIs) and extends the API surface with
fullAccesson the external spawn route andsupportsFullAccessSpawnon the provider capabilities response. It follows the existing convention in this repository, where a release containing afeatchange takes a minor bump (1.11.0 after #158, 1.10.0 after #157, 1.9.0 after #132).Important
#165 must merge before this PR. The branch is cut from main, so merging this first would ship a 1.12.0 that does not contain the feature it is named for.
Schema and rollback
The database migration registry is unchanged from v1.11.1; #165 adds no migration. Schema generation remains 20, and rollback compatibility carries forward every version declared by 1.11.1 plus v1.11.1 itself. The declaration is append-only (16 insertions, 0 deletions), so no published entry is modified.
Verification
npm run release:check-metadata→ passed:Release metadata check passed for 1.12.0 (schema generation 20; 9 rollback-compatible version(s) declared)Run without a canonical declaration or canonical migration registry, so the two immutability warnings are expected in a local run; CI supplies those from the predecessor tag.
npm run verifywas not run for this PR — it only changes version metadata, and #165 already reports a full verify pass on its own branch. Please let CI confirm before merging.🤖 Generated with Claude Code