chore: temp workflow to fire the missed v1.7.0 Discord announce#137
Conversation
Promote RC failed at the merge step twice, so the Discord-announce step in promote.yml never ran for the v1.7.0 stable release. This one-off workflow re-runs just that step against the already-published release. Will be reverted immediately after use.
📝 WalkthroughWalkthroughAdds a manually triggered GitHub Actions workflow that accepts a stable release tag and runs the local Discord release announcement script with configured tokens, channel information, and release metadata. ChangesDiscord release announcement
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/temp-discord-announce.yml:
- Around line 6-9: Constrain the stable_tag workflow input to the intended
validated release by hardcoding v1.7.0, or add a preflight check before the
announcement that accepts only the stable promotion tag and verifies it points
to the release-branch tip. Apply this validation in the workflow
input/announcement path and prevent posting when the check fails.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 3fb95063-69b3-494f-a260-421684841afa
📒 Files selected for processing (1)
.github/workflows/temp-discord-announce.yml
| stable_tag: | ||
| description: "Stable tag to announce (e.g. v1.7.0)" | ||
| required: true | ||
| type: string |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Constrain the input to a validated stable release.
This free-form input can announce any tag without enforcing the documented RC→stable promotion flow or verifying that the stable tag points to the release-branch tip. For this one-off workflow, hardcode v1.7.0 or add a preflight validation before posting.
As per coding guidelines, release workflows must cut release candidates first, promote them to stable, and ensure stable tags point to the release branch tip.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/temp-discord-announce.yml around lines 6 - 9, Constrain
the stable_tag workflow input to the intended validated release by hardcoding
v1.7.0, or add a preflight check before the announcement that accepts only the
stable promotion tag and verifies it points to the release-branch tip. Apply
this validation in the workflow input/announcement path and prevent posting when
the check fails.
Source: Coding guidelines
Its job is done — v1.7.0 stable was announced successfully. See PR #137.
2 participants
Promote RC failed at the merge step twice, so the Discord-announce step in
promote.ymlnever ran for the v1.7.0 stable release (which is already published: https://github.com/getopenscreen/openscreen/releases/tag/v1.7.0). This is a one-off workflow to re-run just that step. Will be removed via a follow-up PR right after use.Summary by CodeRabbit