Skip to content

docs(cli): add release notes generation prompt#5330

Draft
avallete wants to merge 2 commits into
developfrom
claude/release-notes-generator-tHbQ2
Draft

docs(cli): add release notes generation prompt#5330
avallete wants to merge 2 commits into
developfrom
claude/release-notes-generator-tHbQ2

Conversation

@avallete
Copy link
Copy Markdown
Member

Add a comprehensive prompt template for generating user-centric release notes for Supabase CLI releases using an LLM.

This document provides:

  • Input structure — standardized fields for product name, audience, and tone
  • Scope rules specific to the CLI — guidance on filtering next/ shell changes, handling Go-to-TypeScript port PRs, and identifying user-facing changes
  • Investigation process — step-by-step triage and PR analysis workflow to avoid writing from titles alone
  • Classification system — buckets for highlights, features, improvements, bug fixes, breaking changes, and internal work
  • Writing guidelines — voice, structure, and examples showing the transformation from raw PR data to polished release notes
  • Worked examples — 10 detailed before/after examples covering common PR patterns (features, fixes, ports, breaking changes, internal work)
  • Output format — markdown template with sections for breaking changes, highlights, features, improvements, bug fixes, and port progress

The prompt is designed to be pasted into an LLM along with a semantic-release changelog block, producing release notes that answer three key questions for users: "Should I upgrade?", "What can I do now?", and "What gotchas should I know about?"

This replaces the need for manual release note writing and ensures consistency across CLI releases.

https://claude.ai/code/session_01FgZaMWUbVrQaQUFRv9KKYn

claude added 2 commits May 21, 2026 09:01
Adds a prompt template at tools/release/release-notes-prompt.md for
rewriting semantic-release output into user-centric GitHub Release notes.
Pre-fills supabase/cli inputs, scopes user-facing reporting to the legacy
shell, and folds Go-to-TS port PRs into a short port-progress section so
they don't masquerade as user-visible features or fixes.
Adds a propose -> review -> apply pipeline so stable releases get notes
rewritten from the raw semantic-release block into user-centric prose
without blocking distribution. New pieces:

- `apps/cli/scripts/propose-release-notes.ts` re-derives the raw notes,
  inlines them into `tools/release/release-notes-prompt.md`, runs the
  Claude Agent SDK with WebFetch/Bash, and opens a PR adding
  `release-notes/v<VERSION>.md`. Supports `--render-only` for prompt
  iteration without an LLM call.
- `apps/cli/scripts/apply-release-notes.ts` pushes a `release-notes/`
  file to the GitHub Release body via `gh release edit`.
- `.github/workflows/propose-release-notes.yml` (reusable) wraps the
  proposer; non-blocking so an LLM hiccup never gates a published
  release. Stable releases only.
- `.github/workflows/apply-release-notes.yml` triggers on merged PRs
  touching `release-notes/**` and applies each touched file.
- `release-shared.yml` calls the proposer after `backfill-release-notes`
  succeeds.
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.

2 participants