Skip to content

Isolate PartyKit deploy auth env#41

Merged
alowpoly merged 1 commit into
mainfrom
deploy-partykit-worker-auth-env
Jun 27, 2026
Merged

Isolate PartyKit deploy auth env#41
alowpoly merged 1 commit into
mainfrom
deploy-partykit-worker-auth-env

Conversation

@alowpoly

Copy link
Copy Markdown
Contributor

Summary

  • unset Cloudflare R2 env vars for the PartyKit deploy step
  • keep R2 upload env scoped away from PartyKit auth selection

Validation

  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/deploy.yml"); puts "deploy-yaml-ok"'\n- git diff --check -- .github/workflows/deploy.yml\n\n## Root cause\nThe Deploy job sets Cloudflare R2 credentials globally. PartyKit CLI sees CLOUDFLARE_ACCOUNT_ID / CLOUDFLARE_API_TOKEN and takes the Cloudflare Workers auth route instead of the PartyKit token route. That is why local deploy with PartyKit token worked while GitHub Actions failed with Authentication error.

@alowpoly alowpoly merged commit 28e433f into main Jun 27, 2026
1 check passed
@alowpoly alowpoly deleted the deploy-partykit-worker-auth-env branch June 27, 2026 20:33
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