Skip to content

chore: temp workflow to fire the missed v1.7.0 Discord announce #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
EtienneLescot merged 1 commit into from
Jul 19, 2026
Merged

chore: temp workflow to fire the missed v1.7.0 Discord announce #137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions .github/workflows/temp-discord-announce.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
name: TEMP - Announce stable on Discord

on:
workflow_dispatch:
inputs:
stable_tag:
description: "Stable tag to announce (e.g. v1.7.0)"
required: true
type: string
Comment on lines +6 to +9

@coderabbitai coderabbitai Bot Jul 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 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


permissions:
contents: read
issues: read

jobs:
announce:
name: Announce stable on Discord
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4

- name: Setup Node.js
uses: ./.github/actions/setup

- name: Announce stable on Discord
env:
DISCORD_BOT_TOKEN: ${{ secrets.DISCORD_BOT_TOKEN }}
DISCORD_RELEASE_CHANNEL_ID: ${{ vars.DISCORD_RELEASE_CHANNEL_ID }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
STABLE_TAG: ${{ inputs.stable_tag }}
KIND: stable
run: node .github/scripts/discord-release-announce.mjs
Loading