The release workflow passes its notes by file, caps a long page and checks the release exists (#1154) #1155

Merged

claude-bot merged 1 commit from fix/1154-release-notes-by-file into main 2026-10-13 00:54:21 +00:00

Conversation 0 Commits 1 Files changed 5 +342 -71

claude-bot commented 2026-10-13 00:18:28 +00:00

Collaborator

Copy link

Fixes #1154.

The failure

On v4.5.0 the "Create Forgejo release" job died with exec /usr/bin/bash: argument list too long: the notes went through a step output into the release action's release-notes input, and the [4.5.0] section is 344 KB. It had been failing on prereleases too, unnoticed, because the images job succeeded.

What changes

• Notes by file. scripts/changelog.py release-notes --tag … --out release-notes.md writes them; the release is created with the API from that file (jq --rawfile, curl --data-binary). Nothing long travels through an output, an environment value or an argument.
• A capped page. Over 60,000 characters the body is the section's preamble, a count of entries per heading, and a link to the full section at the tag (changelog.d/ for a prerelease). The 4.5.0 section comes out at 1,172 characters. Under the cap, the full notes as before.
• Create or update. A release that already exists for the tag (a re-run, or v4.5.0's hand-made one) is updated, not a failure.
• A missing release turns the job red: a last step reads the release back and checks the tag and a non-empty body.
• docs/OPERATIONS.md: both release procedures gain "check the release page exists".
• The forgejo-release action is no longer used; the job uses the run's own token, as the action did.

Checks

• The changelog script's tests: 26 passed (6 new). Ruff: clean. changelog.py check: OK. The workflow file parses.
• Not run: the workflow itself. It only runs on a tag, so its first real run is v4.5.1-rc1. Not confirmed: that the run's token may write releases through the API directly (the action used the same token), and that jq is on the runner image.

🤖 Generated with Claude Code

Fixes #1154. ## The failure On `v4.5.0` the "Create Forgejo release" job died with `exec /usr/bin/bash: argument list too long`: the notes went through a step output into the release action's `release-notes` input, and the `[4.5.0]` section is 344 KB. It had been failing on prereleases too, unnoticed, because the images job succeeded. ## What changes - **Notes by file.** `scripts/changelog.py release-notes --tag … --out release-notes.md` writes them; the release is created with the API from that file (`jq --rawfile`, `curl --data-binary`). Nothing long travels through an output, an environment value or an argument. - **A capped page.** Over 60,000 characters the body is the section's preamble, a count of entries per heading, and a link to the full section at the tag (`changelog.d/` for a prerelease). The 4.5.0 section comes out at 1,172 characters. Under the cap, the full notes as before. - **Create or update.** A release that already exists for the tag (a re-run, or `v4.5.0`'s hand-made one) is updated, not a failure. - **A missing release turns the job red:** a last step reads the release back and checks the tag and a non-empty body. - `docs/OPERATIONS.md`: both release procedures gain "check the release page exists". - The `forgejo-release` action is no longer used; the job uses the run's own token, as the action did. ## Checks - The changelog script's tests: 26 passed (6 new). Ruff: clean. `changelog.py check`: OK. The workflow file parses. - **Not run: the workflow itself.** It only runs on a tag, so its first real run is `v4.5.1-rc1`. Not confirmed: that the run's token may write releases through the API directly (the action used the same token), and that `jq` is on the runner image. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit 2026-10-13 00:18:29 +00:00

fix(repo): release notes go through a file and the API, capped in size (#1154) ... ae9439daa6

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

claude-bot scheduled this pull request to auto merge when all checks succeed 2026-10-13 00:18:35 +00:00

claude-bot merged commit 87a14cd01d into main 2026-10-13 00:54:21 +00:00

claude-bot referenced this pull request from a commit 2026-10-13 00:54:22 +00:00

Merge PR #1155: the release workflow passes its notes by file, caps a long page and checks the release exists (#1154)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

backend

Issue related to the backend

  

bot

Issue related to the bot

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

frontend

Issue related to the frontend

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

recording

Issue related to the recording system

  

security

Security hardening / vulnerability work

  

wontfix

This won't be fixed

No labels

backend

bot

bug

duplicate

enhancement

frontend

help wanted

invalid

question

recording

security

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

rbrooks/Quest-Board!1155

No description provided.