feat(ci): surface warning when AI release summary is skipped - #42
Open
drewferg11-hermes-bot[bot] wants to merge 1 commit into
Open
feat(ci): surface warning when AI release summary is skipped#42drewferg11-hermes-bot[bot] wants to merge 1 commit into
drewferg11-hermes-bot[bot] wants to merge 1 commit into
Conversation
The AI release summary step uses actions/ai-inference@v1 with GitHub Models (openai/gpt-4o-mini), which is being retired — the v1.4.0-rc.0 release silently published without a Summary section because the inference call hit a 410 "scheduled retirement brownout" and continue-on-error: true swallowed the failure. This modifies render_release_notes.py to emit a ::warning:: workflow annotation when the AI summary file is missing or empty, so the silent omission is visible on the Actions run summary page instead of buried in step annotations. The warning fires at the exact point where the empty summary matters (when rendering release notes). Does not block the release — the script still omits the Summary section and exits normally, it just prints the warning to stdout, which GitHub Actions captures as an annotation on the workflow run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The v1.4.0-rc.0 release silently published without a Summary section. The root cause: the
AI release summarystep inrelease.ymlusesactions/ai-inference@v1with GitHub Models (openai/gpt-4o-mini), which is being retired — the inference call hit a410 "scheduled retirement brownout". Because the step hascontinue-on-error: true, the failure was swallowed,ai-summary.txtwas written as empty, andrender_release_notes.pysilently omitted the Summary section.The workflow run showed green ✓ with 2 errors buried in the Annotations tab — easy to miss.
Solution
Rather than modifying the workflow file (which the GitHub App can't push — workflow files require a separate
workflowspermission), this puts the warning inrender_release_notes.py— the script that already readsai-summary.txtand is called by the workflow'srun:step.When the AI summary file is missing or empty, the script now prints a
::warning::workflow annotation to stdout. GitHub Actions captures these from anyrun:step's output, so the warning appears as a yellow annotation on the Actions run summary page — visible at a glance, not buried.Two cases are handled:
::warning::AI release summary file is missing...::warning::AI release summary was unavailable (empty file)...What this does NOT do
Testing
The
::warning::annotation format is GitHub Actions standard — any line printed to stdout matching::warning::messagewithin arun:step is captured as a workflow annotation. This works from Python scripts called withinrun:steps.Follow-up
The real fix for the missing summaries is either:
actions/ai-inference@v1to a direct OpenAI API call with a repo secret (OPENAI_API_KEY)This PR is just the visibility layer so you know when it happens.