Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

CI deploy fails with "Cloudflare session has no bearer for version-aware upload" (runner-only; passed 10h earlier with the same token)

未關閉
  • 哪裡不對？
#627 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
bun, github-actions, typescript
領域
devops, infrastructure

研究方向

Start by reading the Cloudflare deploy transport in deploy-transport-JCxw7QDi.mjs, especially deployChildEnv and runWranglerAuthToken, then trace the upload and trigger-sync recovery paths. Compare behavior with and without CLOUDFLARE_API_TOKEN in a fresh checkout and inspect how version bindings and secrets are preserved. Done means CI can upload with the environment token and recovery does not activate a version missing the previous bindings.

由索引模型根據 Issue 內容生成。

描述

What happened

void deploy --platform cloudflare (void 1.3.0, GitHub Actions, ubuntu-latest, bun 1.4.3) fails at the very start of the upload step:

◇ Checking the current Worker deployment...   (12 s)
◇ Uploading the Worker and assets...          (0.2 s)
■ Worker deployment stopped.
deploy: Cloudflare Worker Version upload failed (exit 1); production traffic is unchanged.
Cloudflare session has no bearer for version-aware upload.

The same workflow uploaded and activated successfully ~13 hours earlier (2026-10-27 12:52 UTC) with the same CLOUDFLARE_API_TOKEN secret, same repo config, same workflow file. Between the two runs nothing on the repo/auth side changed; the second failure then reproduced identically on three consecutive runs.

Repro status
  • Not reproducible locally: a fresh git archive of the same commit (no .void/ state, i.e. exactly the CI checkout), bun install, then CLOUDFLARE_API_TOKEN=<same shape: user token, Edit Cloudflare Workers template> bunx void deploy --platform cloudflare succeeds on macOS (pinned upload path included — usesCf is structural, so runWranglerAuthToken resolved the api_token fine).
  • On the runner the same getToken() (runWranglerAuthToken → wrangler auth.token under deployChildEnv) returns null.
Suspected cause

deployChildEnv hardcodes CLOUDFLARE_AUTH_USE_KEYRING = "true" (deploy-transport-JCxw7QDi.mjs). On a headless GitHub runner there is no user keyring session; if wrangler's keyring init fails/hangs there, auth.token exits non-clean and runWranglerAuthToken returns null → "no bearer". On macOS (local repro) the keyring exists, so the env-token path proceeds. Consistent with "worked at 12:52, broke later with zero auth-side change" if a runner image roll changed the keyring situation.

Request: when CLOUDFLARE_API_TOKEN is present in the environment, either don't force the keyring, or fall back from the pinned uploader to the plain wrangler upload instead of failing.

Second issue hit on the same integration

The earlier 12:52 run got past upload and activation but failed at trigger synchronization; the recovery left an empty, binding-less version active (no main, no assets, compat date defaulted to 2026-10-19), which replaced our production worker and wiped both Worker secrets until we redeployed manually. void's upload patch sets keep_vars: true but never keep_secrets, and the fresh-checkout CI path has no .void/ link state. Two suggestions: (1) the trigger-sync recovery should re-activate the previous version's full bindings, not an empty shape; (2) uploads from a fresh checkout should preserve secret_text bindings the way they preserve vars.

Happy to provide the JSONL logs (sanitized) — the top-level events only show deploy_start → deploy_target → cloudflare_deploy_start → cloudflare_deploy_failed; no per-child detail is mirrored even with --debug.

主要語言
TypeScript
星號
580
分支
56
平均合併
11 小時 32 分鐘
30 天內合併 PR
158

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

voidzero-dev/void 的其他 Issue

查看 voidzero-dev/void 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。