Skip to content

Remove automated release-notes workflow - #1114

Open
KaladinX wants to merge 1 commit into
mainfrom
remove-auto-release-notes
Open

Remove automated release-notes workflow#1114
KaladinX wants to merge 1 commit into
mainfrom
remove-auto-release-notes

Conversation

@KaladinX

Copy link
Copy Markdown
Contributor

What

Deletes .github/workflows/release-notes.yml — the workflow that, on each release tag, summarized the commit log with Gemini and posted the result to Discord through the n8n webhook.

Why

The team prefers writing release announcements manually: paste the commit log into any LLM, edit, and post. That keeps editorial control over what users see and removes a pipeline (Gemini API + n8n webhook) we no longer want to maintain.

What is not affected

  • auto-tag.yml stays — tag-build.yml still builds releases from the tags it creates.
  • pr-build.yml's "Generate release notes" step stays — that's GitHub's built-in generate-notes used for pre-release bodies, unrelated to the AI summarizer.
  • The in-editor "Release Notes" update-notification button (docs/update-system.md) is a separate feature and untouched.

Cleanup this enables (not done here)

  • Repo secrets GEMINI_API_KEY and N8N_WEBHOOK_URL, and repo variable GEMINI_MODEL, are now unused and can be deleted in repo settings.
  • The n8n Discord workflow that received these payloads can be retired.

🤖 Generated with Claude Code

Problem: on every release tag, the "Generate and Send Release Notes"
workflow collected the commit log, summarized it with the Gemini API,
and posted the result to Discord via an n8n webhook. The team has
decided the automated summaries aren't worth maintaining — devs prefer
to paste the commit log into whatever LLM they like and write the
announcement by hand, which gives them editorial control over what
users see.

Change: delete .github/workflows/release-notes.yml. Nothing else
depended on it — auto-tag.yml stays because tag-build.yml still uses
the tags it creates, and pr-build.yml's "release notes" step is
GitHub's plain generate-notes for prerelease bodies, unrelated to this
workflow.

Follow-ups this unlocks (outside this repo): the GEMINI_API_KEY and
N8N_WEBHOOK_URL repo secrets and the GEMINI_MODEL repo variable are now
unused and can be removed, and the n8n Discord workflow will simply
stop receiving calls.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@KaladinX
KaladinX requested a review from LeviXIII July 23, 2026 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant