feat(ci): add Release Automation Regression canary + rename VF canary#214
Merged
hdamker merged 2 commits intocamaraproject:validation-frameworkfrom Apr 22, 2026
Merged
Conversation
Prep for sibling Release Automation Regression canary in the next commit — the parallel naming groups both regression workflows together in the Actions UI and distinguishes their surfaces (validation rules vs release automation runtime). Script name (validation/scripts/regression_runner.py) unchanged; it describes script behavior, not workflow identity.
New workflow fires a /create-snapshot + /discard-snapshot round-trip on camaraproject/ReleaseTest whenever pushes to validation-framework touch RA-surface paths (release-automation-reusable.yml, release_automation/**, shared-actions/**, tooling_lib/**). Catches runtime bugs that escape the Validation Regression canary — classes demonstrated by tooling#197 (validate-command SyntaxError) and tooling#198 (tooling_lib missing from sparse-checkout), both of which sat dormant for 3 days before a manual test surfaced them. Round-trip only; merging the Release Review PR and /publish-release remain out of scope — full manual E2E still gates @v1-rc moves for publish-side changes. Uses the existing camara-validation App token (actions:write + issues:write + pull_requests:write), same pattern as validation-regression.yml.
This was referenced Apr 22, 2026
Merged
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
1 participant
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.
What type of PR is this?
enhancement/feature
What this PR does / why we need it:
Adds a second regression canary on
validation-frameworkcovering the Release Automation surface. The existing canary only exercisescamara-validation.yml— runtime bugs inrelease-automation-reusable.ymlcan sit dormant for days (recent examples: #197, #198, both 3 days dormant).The new Release Automation Regression workflow fires a
/create-snapshot+/discard-snapshotround-trip oncamaraproject/ReleaseTestwhenever a push tovalidation-frameworktouches RA-surface paths (release-automation-reusable.yml,release_automation/**,shared-actions/**,tooling_lib/**). Both #197 and #198 would have been caught pre-merge.Round-trip only — merging the Release Review PR and
/publish-releaseremain out of scope; full manual E2E still gates@v1-rcmoves.For symmetry the existing VF canary is renamed:
regression-runner.yml→validation-regression.ymlrelease-automation-regression.ymlUses the existing
camara-validationApp token, same permission profile as the renamed sibling.Which issue(s) this PR fixes:
Fixes #
Related to camaraproject/ReleaseManagement#379 — adds CI regression coverage to improve RA rollout reliability.
Special notes for reviewers:
release-review/<id>-preservedbranch behind per normal/discard-snapshotsemantics.release-state:planned, the runner exits 2 without mutating anything — avoids stomping on a manual cycle.regression-runner.ymlpath 404s; artifact name changesregression-runner-summary→validation-regression-summary.release_automation/tests/tests pass; 24 existing VF tests pass post-rename.Changelog input
Additional documentation
This section can be blank.