Skip to content

fix(tooling): let production bootstrap continue without cf login - #68

Merged
WillieCubed merged 1 commit into
mainfrom
codex/cf-bootstrap-auth
Sep 30, 2026
Merged

WillieCubed merged 1 commit into
mainfrom
codex/cf-bootstrap-auth

Conversation

@WillieCubed

@WillieCubed WillieCubed commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

TL;DR

pnpm bootstrap --production can reach Turnstile and Access setup with an account-owned setup token even when cf has no local login.

Overview of Changes

The machine check now warns about missing cf authentication during production bootstrap, allowing independent platform setup steps to run. Cf commands that create or migrate D1 and R2 resources still need their own credential. Ordinary preflight remains strict, and an explicitly invalid account token no longer counts as an authenticated cf session.

This includes a regression test, updated command guidance, and the required 0.6.2 package and example pins. pnpm check passed with 274 CLI tests and 79 web-platform tests.

Follow-ups

None.

Production bootstrap can use a scoped account setup token for Turnstile
and Access while cf has no local login. Report that missing login as a
warning and leave cf-only D1 and R2 operations to their own credential.
Reject cf identity output that explicitly marks an API token invalid.

Co-authored-by: Codex <noreply@openai.com>
@WillieCubed
WillieCubed force-pushed the codex/cf-bootstrap-auth branch from c190202 to 9be0e56 Compare September 30, 2026 05:22
@WillieCubed
WillieCubed merged commit 7a3f689 into main Sep 30, 2026
1 check passed
@WillieCubed
WillieCubed deleted the codex/cf-bootstrap-auth branch September 30, 2026 05:26
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