From 48f203120d872776bc80ce4327c5066d513a74e9 Mon Sep 17 00:00:00 2001 From: Michael Bolin Date: Thu, 29 Jan 2026 11:51:33 -0800 Subject: [PATCH 1/2] fix: unify `npm publish` call across shell-tool-mcp.yml and rust-release.yml (#10182) We are seeing flakiness in the `npm publish` step for https://www.npmjs.com/package/@openai/codex-shell-tool-mcp, so this is a shot in the dark for a fix: https://github.com/openai/codex/actions/runs/21490679301/job/61913765060 Note this removes `actions/checkout@v6` and `pnpm/action-setup@v4` steps, which I believe are superflous for the `npm publish` call. --- .github/workflows/shell-tool-mcp.yml | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/.github/workflows/shell-tool-mcp.yml b/.github/workflows/shell-tool-mcp.yml index d6c85d9ddc..6285754fb0 100644 --- a/.github/workflows/shell-tool-mcp.yml +++ b/.github/workflows/shell-tool-mcp.yml @@ -436,14 +436,6 @@ jobs: id-token: write contents: read steps: - - name: Checkout repository - uses: actions/checkout@v6 - - - name: Setup pnpm - uses: pnpm/action-setup@v4 - with: - run_install: false - - name: Setup Node.js uses: actions/setup-node@v6 with: @@ -451,6 +443,10 @@ jobs: registry-url: https://registry.npmjs.org scope: "@openai" + # Trusted publishing requires npm CLI version 11.5.1 or later. + - name: Update npm + run: npm install -g npm@latest + - name: Download npm tarball uses: actions/download-artifact@v7 with: From ce02159f6002c27e3d56caa2964210f14b12180b Mon Sep 17 00:00:00 2001 From: Michael Bolin Date: Thu, 29 Jan 2026 12:25:55 -0800 Subject: [PATCH 2/2] fix: /approvals -> /permissions --- codex-rs/tui/tooltips.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/codex-rs/tui/tooltips.txt b/codex-rs/tui/tooltips.txt index dc2d2faa67..455ae5cd03 100644 --- a/codex-rs/tui/tooltips.txt +++ b/codex-rs/tui/tooltips.txt @@ -2,7 +2,7 @@ Use /compact when the conversation gets long to summarize history and free up co Start a fresh idea with /new; the previous session stays in history. Use /feedback to send logs to the maintainers when something looks off. Switch models or reasoning effort quickly with /model. -Use /approvals to control when Codex asks for confirmation. +Use /permissions to control when Codex asks for confirmation. Run /review to get a code review of your current changes. Use /skills to list available skills or ask Codex to use one. Use /status to see the current model, approvals, and token usage.