Skip to content

fix(release): settle confirm-main on the release leaf job, not the first 'release' match - #3103

Merged
wphillipmoore merged 1 commit into
developfrom
feature/3102-confirm-release-leaf
Oct 6, 2026
Merged

wphillipmoore merged 1 commit into
developfrom
feature/3102-confirm-release-leaf

Conversation

@wphillipmoore

Copy link
Copy Markdown
Collaborator

Pull Request

Summary

  • confirm-main now waits for the job identified by _is_release_job (leaf segment 'release') instead of the first job whose name contains 'release', so cd-release's new package jobs (vergil-actions#905) can no longer end the settle wait before release / release concludes.

Issue Linkage

Notes

…rst 'release' match

confirm_main waited for the first job whose name contained 'release'. With vergil-actions#905, cd-release adds release / package-matrix (always runs, finishes first) plus package-build/package-sign jobs, so the settle wait could end before release / release concluded and the release would fail falsely (a regression of the #1611 race).

_settled_run_jobs now takes job matchers (predicates on the job name). confirm-main settles on _is_release_job (the leaf-segment matcher that already handles release / release and cd / release, #2001); confirm-develop keeps its substring match via _name_contains('docs').

Ref #3102
@wphillipmoore
wphillipmoore merged commit 8db1260 into develop Oct 6, 2026
30 checks passed
@wphillipmoore
wphillipmoore deleted the feature/3102-confirm-release-leaf branch October 6, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

confirm-main must settle on the release job by leaf name, not the first job containing 'release'

1 participant