Skip to content

ci: a suffixed release tag falls back to the final release's notes file - #45

Merged
zeyuyang42 merged 1 commit into
mainfrom
release-notes-fallback
Oct 16, 2026
Merged

zeyuyang42 merged 1 commit into
mainfrom
release-notes-fallback

Conversation

@zeyuyang42

Copy link
Copy Markdown
Collaborator

Follow-up to the max-v0.3.0-rc1 dry run (2026-10-16), which produced the right draft, asset and prerelease flag but the placeholder body, because the release job only looked for docs/releases/max-v0.3.0-rc1.md.

The job now tries, in order: the tag's own file, docs/releases/<host>-v<version with the -suffix stripped>.md, then the placeholder, which now names that final file. host and version come from the guard step's outputs. One sentence added to rule 4 in docs/design/release-process.md.

Checked locally with the extracted selection logic: max-v0.3.0 → own file; max-v0.3.0-rc1 and max-v0.3.0-rc1-fix → max-v0.3.0.md; pd-v0.3.0-rc1 with no Pd notes → placeholder naming pd-v0.3.0.md. The workflow file still parses.

🤖 Generated with Claude Code

max-v0.3.0-rc1 looked for docs/releases/max-v0.3.0-rc1.md only, so every dry run
showed the placeholder instead of the notes it is meant to rehearse. The release
job now tries the tag's own file, then <host>-v<version-without-suffix>.md, then
the placeholder, which names that final file.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@zeyuyang42
zeyuyang42 merged commit 8aa274f into main Oct 16, 2026
8 checks passed
@zeyuyang42
zeyuyang42 deleted the release-notes-fallback branch October 16, 2026 23:33
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