ci: wire the real release deployment signal - #678
Merged
Conversation
Signed-off-by: Swarom Muley <smuley@nvidia.com>
Signed-off-by: Swarom Muley <smuley@nvidia.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe release workflow now conditionally dispatches a deployment signal after successful final artifact polling for non-dry-run Helm releases. The release guide documents downstream pending-deployment creation and independent completion by the deployment controller. ChangesHelm deployment signaling
Sequence Diagram(s)sequenceDiagram
participant ReleaseWorkflow
participant ReleaseRepository
participant DeploymentController
ReleaseWorkflow->>ReleaseRepository: Dispatch create-release-deployment with stage-helm version
ReleaseRepository->>DeploymentController: Create pending GitHub Deployment
DeploymentController->>ReleaseRepository: Complete deployment
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
svvarom
enabled auto-merge
July 14, 2026 17:36
Contributor
|
This was referenced Jul 15, 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
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.
The nightly run showed Signal deployment as skipped. That looked like the real deployment handoff, but inspection revealed it was still an echo-only placeholder; the actual dispatch lived in a separate job with a different name.
Consolidating those jobs exposed the reason both had skipped: nightlies intentionally skip stable-only release registration, and GitHub propagates that skipped state through dependent jobs unless they explicitly evaluate their own status. Artifact polling already handled that case and succeeded, but deployment signaling did not.
This PR makes the real dispatch the single
signal-deploymentjob. It now runs only when the workflow was not cancelled, artifact polling succeeded, Helm was selected, and the run is not a dry run. The final notification therefore observes the job that actually performs the handoff.create-release-deploymentwith the source SHA, cadence, release label, and Helm versionThe downstream workflow remains responsible for creating the pending GitHub Deployment and completing it independently.
Evidence
actionlint .github/workflows/release.yamlpasses.Linear: AIREINF-267 — Create the deployment workflow