The v3.0.2 announce (PR #263, 45 commits) never reached Discord: the
changelog prompt carried every commit body (52 KB), deepseek-v4-flash
spent its whole 6000-token budget reasoning, returned empty content and
the guard aborted the run before posting.
Past 8000 chars of commit detail we now send hash + subject only (52916
-> 3699 chars on that range), raise the budgets to 32000/16000, and retry
once with double when content still comes back empty. Also log
finish_reason and completion_tokens so the next empty answer is
diagnosable from the run log alone.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- Reorder: send Discord FIRST; commit CHANGELOG + version bump ONLY on
a successful announce, so a failed send never consumes a version.
- Raise max_tokens for the deepseek-v4-flash reasoning model (6000/4000)
so reasoning+content fit and content is never empty.
- Guard against empty content (don't POST an empty Discord message).
- Add workflow_dispatch (manual re-fire) with an optional base ref input.
Seed the release branch with the corrected discord-release-notify workflow
and version baseline BEFORE the next master->release merge, so that merge
announces v3.0.0 and the workflow bumps the patch (3.0.0 -> 3.0.1 -> ...)
on every subsequent merge instead of repeating the same version.
A direct push (not a pull_request) does not trigger the announce workflow,
so this is safe to land here ahead of the merge.
David Montero