Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの 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 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR（30日）
158

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

voidzero-dev/void のほかの issue

voidzero-dev/void の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。