t3532: fix concurrency group in publish-packages and postflight workflows#4710
Conversation
…cancellation of distinct manual runs Closes #3532 publish-packages.yml: group now includes ${{ github.event.inputs.version || github.sha }} postflight.yml: group now includes ${{ github.event.inputs.tag || github.sha }} Without this, two manual workflow_dispatch runs with different version/tag inputs shared the same concurrency group and the second would cancel the first.
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Sat Mar 14 08:09:27 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
…cancellation of distinct manual runs (#4710) Closes #3532 publish-packages.yml: group now includes ${{ github.event.inputs.version || github.sha }} postflight.yml: group now includes ${{ github.event.inputs.tag || github.sha }} Without this, two manual workflow_dispatch runs with different version/tag inputs shared the same concurrency group and the second would cancel the first.



Summary
version/tagworkflow_dispatch input into the concurrency group key so distinct manual runs no longer cancel each othergithub.shafor release-triggered runs (where no input is provided), preserving existing deduplication behaviour for automated triggersChanges
publish-packages.yml${{ github.workflow }}-${{ github.ref }}postflight.yml${{ github.workflow }}-${{ github.ref }}Why
Two
workflow_dispatchruns targeting different versions (e.g., re-publishing v2.51.0 while v2.52.0 is in flight) shared the same concurrency group and the second would cancel the first. The fix makes each distinct version/tag input produce a unique group key.Closes #3532