fix(ci): treat an up-to-date dependabot branch as update success - #149
Merged
Merged
Conversation
update-branch answers 422 'no new commits on the base branch' when the bound pull request is already current. That string matched neither the 'already up to date' success pattern nor a real failure, so the step exited 1 and the convergence job never ran the catalog sync -- leaving setup-uv v10.2.0 workflows with a v10.1.0 catalog on #145. Signed-off-by: rldyourmnd <danil@nddev.it.com>
This was referenced Oct 4, 2026
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
The convergence job for dependabot bumps died on #145:
update-branchanswered422 no new commits on the base branch— the branch was already current — but the guard only accepted the literalalready up to datestring, so it exited 1 before the catalog sync ran. Catalog stayed at setup-uvv10.1.0while workflows carriedv10.2.0, failingtool-registryandcatalogcore validators.The fix normalizes both up-to-date replies to the existing success marker, so the poll resolves immediately instead of timing out on an update that never ran.
Permissions diff
None — same
pull-requests: writecall, same error surface, only the accept-set widened to the API's second success phrasing.Threat-model note
The step still writes only to the one open pull request bound to
workflow_run.head_branchafter verifyinghead.shamatches the triggering run; widening the accept-string cannot grant pushes elsewhere.Test plan
422 no new commits on the base branchGenerated with Devin