[codex] Enforce GCP release lab artifacts#108
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Validation update before merge:
Next after merge: dispatch the non-dry |
adamcohenhillel
marked this pull request as ready for review
July 2, 2026 11:42
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR corrects the release/lab path so OpenPhone release publishing is explicitly GCP-backed instead of silently dispatching the Android compile to an ambiguous self-hosted build runner.
It:
scripts/lab/gcp/run-release.shto create a disposable GCP VM, use warm cache state, build target-files/OTA tooling, run the emulator gate, copy artifacts back, and clean up;scripts/stage-release-ota.shto stage an OTA from target-files using Android releasetools instead of relying on the Lineagebaconwrapper as the artifact contract;openphone-buildare not described as the official OpenPhone CI/CD path.Why
The previous release workflow looked GCP-related, but the real Android compile still used
runs-on: [self-hosted, openphone-build], which resolved to non-GCP infrastructure. That defeated the goal: trusted PRs and releases need evidence from a real GCP build/emulator path, not a shallow smoke or hidden runner.Validation
bash -n scripts/stage-release-ota.sh scripts/lab/gcp/run-release.sh scripts/lab/gcp/run-smoke.sh scripts/check-assistant-java.sh scripts/bootstrap-android-build-host.sh.github/workflows/release.ymland.github/workflows/gcp-lab.ymlgit diff --check./scripts/check.sh./scripts/check-release-notes.sh v0.0.2 docs/releases/0.0.2.mdgh release view v0.0.2still reportsrelease not foundRemaining Before Merge
v0.0.2only after that GCP build/emulator/release path passes.