Fold greenlight lambda into the shared lambda release - #8612
Merged
Conversation
**Impact:** CI/release tooling only — greenlight deployment flow and its docs **Risk:** low ## What Retires the standalone `greenlight-lambda-release.yml` workflow and moves the greenlight zip build into the shared lambda release (`_lambda-do-release-runners.yml`) as a new `build-greenlight-lambda` job, so `greenlight-scan.zip` is published alongside every other lambda under a single `v<timestamp>` tag. Also adds `greenlight/**` to the paths that trigger the release-tag workflow. ## Why Greenlight had its own manual `workflow_dispatch` release cutting `greenlight-lambda-v<timestamp>` tags, separate from the shared lambda release. Consolidating means one tag, one Release carrying all lambda zips, and an automatic cut on any push to `main` that touches `greenlight/**` — no more remembering to run a dedicated workflow. # Notes - The greenlight leg keeps its own mise/uv/just (cp313) toolchain and smoke test rather than the `make deployment.zip` convention, so it's a dedicated job instead of a matrix entry. - It runs `continue-on-error: true` (same rationale as the advisor-coverage leg): a broken greenlight build omits its zip from the Release instead of blocking the other lambdas. Operators should confirm `greenlight-scan.zip` is present before pinning a tag in the `pytorch-gha-infra-2` Terrafile. - README and CHEATSHEET updated to describe the new flow. Signed-off-by: Jean Schmidt <contato@jschmidt.me>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
meta-cla
Bot
added
the
CLA Signed
huydhn
approved these changes
Aug 24, 2026
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
2 participants
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.
Impact: Lambda release tooling
Risk: low
What
Retires the standalone
greenlight-lambda-release.ymlworkflow and moves the greenlight zip build into the shared lambda release (_lambda-do-release-runners.yml) as a newbuild-greenlight-lambdajob, sogreenlight-scan.zipis published alongside every other lambda under a singlev<timestamp>tag. Also addsgreenlight/**to the paths that trigger the release-tag workflow.Why
Greenlight had its own manual
workflow_dispatchrelease cuttinggreenlight-lambda-v<timestamp>tags, separate from the shared lambda release. Consolidating means one tag, one Release carrying all lambda zips, and an automatic cut on any push tomainthat touchesgreenlight/**— no more remembering to run a dedicated workflow.