Repository navigation
v2.23.3
What's new
Bug Fixes
The third hotfix in the release-notes-narrative v2 automation chain resolves the final blocker preventing fully automated post-release narrative generation.
After v2.23.2 published (which fixed the missing dispatch-release-notes.sh script), the Release CI job was still failing with HTTP 422: Unexpected inputs provided: ["correlation-id"]. The root cause: dispatch-release-notes.sh passes a UUID correlation token as a structured -f correlation-id=... workflow dispatch field so that the polling loop can identify the correct Fro Bot run, but fro-bot.yaml had never declared correlation-id as a known input. GitHub's Actions runtime validates every field in a workflow_dispatch or workflow_call invocation against the workflow's declared inputs: block and rejects any unrecognized name.
This fix adds correlation-id as an optional string input to both the workflow_dispatch and workflow_call entry points in fro-bot.yaml. The field is purely a polling correlation primitive — Fro Bot echoes it as its first log line so the dispatching script can scan early job output and match the run unambiguously, eliminating same-second collision risk. No existing entry point (PR comments, issue events, scheduled maintenance) is affected; they simply omit the field, which is valid for an optional input.
With this declaration in place, the end-to-end acceptance gate for v2 — where a published release automatically triggers Fro Bot to rewrite its notes — can proceed without operator intervention.