Gate releases on vendored template integrity - #514
Draft
jdchawla29 wants to merge 1 commit into
Draft
Conversation
New reusable templates-integrity workflow: install each environments/ template with hud overridden by the checkout (nightly/manual) or the built wheel (release gate), run its test suite, and build its Docker image. release.yml publishes only after the gate passes against the exact wheel being released; the nightly schedule catches drift between releases.
jdchawla29
marked this pull request as draft
July 27, 2026 03:21
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.
Stacked on #513.
Adds
.github/workflows/templates-integrity.yml, a reusable workflow that for eachenvironments/template: installs its pinned deps, overrideshudwith either the repo checkout (nightly, manual dispatch) or the built wheel (source: wheel), runs the template's test suite, and builds itsDockerfile.hudimage.release.ymlnow runs it as atemplate-gatejob withsource: wheelanddeploydepends on it — a wheel that breaks a canonical template, or a template image that no longer builds, cannot be published. The nightly schedule surfaces the same drift between releases instead of on release day.Notes:
hudfrom PyPI at image build time, so the gate's docker step exercises the previous release inside the image; the wheel-override applies to the test suite. Aligning the image install with the release candidate is part of the laterhud initvendoring work.Note
Low Risk
Changes are limited to GitHub Actions orchestration; no runtime SDK or application code is modified.
Overview
Release publishing is gated on vendored
environments/templates:release.ymladds atemplate-gatejob that calls the new workflow withsource: wheel, anddeploynowneedsit so PyPI publish only runs after the gate passes.The new
templates-integrity.ymlworkflow runs on a nightly schedule, manual dispatch, and as a reusableworkflow_call. For each matrix template (coding,cua), it syncs pinned deps, installshudfrom the checkout (editable) or fromdist/hud-*.whlwhensourceiswheel, runspytest, and buildsDockerfile.hud.Nightly runs surface SDK–template drift between releases; on release, the gate ensures a wheel that breaks canonical template tests or image builds cannot ship.
Reviewed by Cursor Bugbot for commit 713acdf. Bugbot is set up for automated code reviews on this repo. Configure here.
HUD-2276