Skip to content

Never stop coding. Free MIT AI gateway: one endpoint, 375 providers (150+ free), 1,400+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 900+ contributors

fix(ci): electron-release publish-npm contents:write (#3966)

Diego Rodrigues de Sa e Souzad59cd14391a8
diff --git a/.github/workflows/electron-release.yml b/.github/workflows/electron-release.yml
index 372e093525..156e4ae80e 100644
--- a/.github/workflows/electron-release.yml
+++ b/.github/workflows/electron-release.yml
@@ -268,7 +268,11 @@ jobs:
name: Publish to npm
needs: [validate, release]
permissions:
- contents: read
+ # Must be `write`, not `read`: this job calls the reusable npm-publish.yml whose
+ # `publish` job needs `contents: write` (gh release upload — attach the SBOM, #3874).
+ # A reusable workflow's job cannot request more permission than the caller grants,
+ # so a `read` here makes GitHub reject the run at startup (startup_failure).
+ contents: write
id-token: write # npm provenance (forwarded to the reusable workflow)
packages: write # publish to npm.pkg.github.com
uses: ./.github/workflows/npm-publish.yml