Skip to content

Promote staging to main: opencode Google key mirror - #1268

Merged
dot-agi merged 1 commit into
mainfrom
staging
Aug 14, 2026
Merged

Promote staging to main: opencode Google key mirror#1268
dot-agi merged 1 commit into
mainfrom
staging

Conversation

@charlesyhuang

Copy link
Copy Markdown
Collaborator

Caution

DO NOT USE THE MERGE BUTTON ON THIS PULL REQUEST.
THE BUTTON CREATES A NEW COMMIT AND BREAKS THE RELEASE MODEL.
COMMENT /promote TO COMPLETE THE PROMOTION.

Summary

Ships the follow-up that makes the opencode Google credential fix actually reachable: the platform key is now mirrored onto GOOGLE_GENERATIVE_AI_API_KEY in the worker's os.environ, which is the surface Harbor's opencode agent reads when choosing provider keys to forward.

Commits in this promotion

a406827 Mirror the Google key onto the AI SDK name in the worker environment (#1267)

One commit. main is an ancestor of staging (git merge-base --is-ancestor passes), so this fast-forwards cleanly.

Validation

⚠️ Wait for Staging Deploy to go green on a406827 before commenting /promote. At the time of writing it is still in progress, along with load_only Guard, E2E: CLI smoke and E2E: Dashboard. Branch Sync Guard has already passed. Promotion Preflight re-checks the staging deploy, so an early /promote fails safe rather than shipping unvalidated code.

PR #1267 ran uv run pytest tests/test_harbor_runner.py tests/test_job_tokens.py → 162 passed. The two failures in that file (test_restricted_cursor_gets_transport_hosts_and_web_hardening, test_run_harbor_trial_async_skips_temp_root_preflight_without_task_patch) are pre-existing on main — verified by checking out clean main without the commit and re-running, where they fail identically.

Not soak-tested beyond the automated deploy. The behaviour it fixes can only be exercised by a real opencode + google/ trial, which is the follow-up below.

Follow-up

Once deployed, re-run 2–3 opencode trials in 826d7d88 and confirm input tokens climb above zero — that is the proof the credential reaches the CLI. The prior 160 trials are zero-token infra failures with no salvageable signal and can be deleted.

Independently worth doing: add GOOGLE_GENERATIVE_AI_API_KEY to the oddish-prod Modal secret. This commit makes the platform resilient without it, but an explicit secret is authoritative and this code deliberately never overwrites one.


Generated by Claude Code

@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
oddish-app Ready Ready Preview Aug 14, 2026 9:18pm

@charlesyhuang

Copy link
Copy Markdown
Collaborator Author

/promote

@github-actions

Copy link
Copy Markdown
Contributor

Promoted. main now points at a40682772ac6f49cf6e8f21bee99e29964b64ec4, the same commit as staging.

@dot-agi
dot-agi merged commit a406827 into main Aug 14, 2026
25 checks passed
@railway-app
railway-app Bot temporarily deployed to pleasing-unity / production August 14, 2026 21:24 Inactive
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