Skip to content

Fix deploy: save Void platform connection before void deploy - #536

Merged
Brooooooklyn merged 1 commit into
mainfrom
copilot/fix-deploy-issue
Oct 6, 2026
Merged

Brooooooklyn merged 1 commit into
mainfrom
copilot/fix-deploy-issue

Conversation

Copilot AI commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

The Deploy to Void job on main has failed since the Void 0.26 upgrade. The build succeeds, then void deploy aborts with platform: No connection to https://api.void.cloud. Run void connect … first. Void 0.26 expects a saved platform connection in every fresh CI environment, and the workflow never created one.

Changes

  • .github/workflows/ci.yml (deploy job)
    • New Connect to Void platform step runs before deploy. --no-login records the verified connection without authenticating, so GitHub OIDC still supplies the credentials.
    • The deploy command now passes --platform void, as the 0.26 CI docs show.
    • The "Single step" comment above the deploy step is reworded because deploy is now two steps.
- name: Connect to Void platform
  run: npx void connect "$VOID_API_URL" --no-login

- name: Deploy
  run: npx void deploy --platform void --project "$VOID_PROJECT" --skip-build

Notes for review

  • The change follows the 0.26 docs (guide/deployment.md, reference/cli/deploy.md). It only runs on push to main, so it hasn't been run against the real OIDC exchange. The first main run after merge will confirm it.
  • VOID_API_URL already comes from the job env, so no new secrets or repo variables are needed.

Co-authored-by: Brooooooklyn <3468483+Brooooooklyn@users.noreply.github.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@Brooooooklyn
Brooooooklyn merged commit 1892a5a into main Oct 6, 2026
2 checks passed
@Brooooooklyn
Brooooooklyn deleted the copilot/fix-deploy-issue branch October 6, 2026 16:53
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.

2 participants