fix(ci): generate release notes from docker-publish draft#6263
Merged
gustavosbarreto merged 1 commit intomasterfrom Apr 29, 2026
Merged
fix(ci): generate release notes from docker-publish draft#6263gustavosbarreto merged 1 commit intomasterfrom
gustavosbarreto merged 1 commit intomasterfrom
Conversation
build-agent.yml and docker-publish.yml race to create the GitHub release draft on tag push. Whichever finishes first wins, and the other reuses the existing draft. build-agent has generate_release_notes: true but docker-publish did not, so when docker-publish wins the race the draft ends up with an empty body. Align both workflows so the result is identical regardless of ordering.
|
Claude finished @gustavosbarreto's task in 15s —— View job Code Review CompleteReviewed 1 file across code quality, security, testing, language patterns, and architecture — no issues found. The code looks good as-is. The change correctly aligns |
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
1 participant
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.
Summary
`build-agent.yml` and `docker-publish.yml` both run on tag push and race to create the GitHub release draft. Whichever workflow's `softprops/action-gh-release` step finishes first wins; the other one reuses the existing draft.
Aligning both workflows means the result is identical regardless of ordering.