Skip to content

Release packages - #55

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

grok-bot-cli@0.4.2

Patch Changes

  • f874c4e: Add gbot codex desktop-shim install|uninstall|status: installs a fail-open CODEX_CLI_PATH wrapper plus stdio-to-WebSocket bridge under ~/.codex/bin/ so ChatGPT Desktop shares the managed Codex app-server daemon (stock app-server proxy hangs for Desktop stdio). The wrapper preflights the socket and runs the bridge as a fallible child (no daemon start on the hot path), exports the CODEX_HOME-derived socket, the bridge handshake and first RPC run under absolute deadlines with accept validation and continuation assembly, the stdin commit point is byte-precise, status reads the macOS GUI-domain env, and send no longer answers another client's approvals outside its own turn. macOS persists the GUI env via LaunchAgent; uninstall restores stock Desktop/Codex behavior.

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

Codex Bridge — refresh, do not merge yet

Decision: keep #55 open for the next npm bump; do not merge until Zack explicitly says publish.

Post-#58 main already queued the Changesets Release workflow (35038076319 on 53cfbee). That run should refresh this PR against current main (desktop-shim + potato-mustfix-stack notes). Local Mac/Ubuntu inject is VERIFIED at 0.4.2 pack; npm registry publish remains the fleet gap.

Hard rule: no merge without Zack.

@cursor

cursor Bot commented Sep 16, 2026

Copy link
Copy Markdown

Superseded by #61 — this PR's tip (fbaa643) still releases 0.4.2, but npm already has 0.4.2 and main has since moved on (0.4.2 release 44a3933 + must-fix stack 53cfbee). The fresh 0.4.3 release PR (#61, from changeset version on latest main) carries the correct tip. Closing as superseded; do not merge this one.

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