-
Notifications
You must be signed in to change notification settings - Fork 0
[health-audit] Failed CI on Main #321
Copy link
Copy link
Closed as not planned
Labels
ai:createdAI-generated - Requires human approval before implementationAI-generated - Requires human approval before implementationpriority:highHigh - Should be addressed soon (semver: priority)High - Should be addressed soon (semver: priority)size:xsXS - Trivial change, <1 hourXS - Trivial change, <1 hourtype:ciCI - CI/CD pipeline changesCI - CI/CD pipeline changes
Metadata
Metadata
Assignees
Labels
ai:createdAI-generated - Requires human approval before implementationAI-generated - Requires human approval before implementationpriority:highHigh - Should be addressed soon (semver: priority)High - Should be addressed soon (semver: priority)size:xsXS - Trivial change, <1 hourXS - Trivial change, <1 hourtype:ciCI - CI/CD pipeline changesCI - CI/CD pipeline changes
_release-please-auto-merge.ymlfailures continue on themainbranch. Issue first flagged in #312 (2026-05-14) and re-raised in #318 (2026-05-15); the root cause remains unresolved.Current State
Since the last audit (2026-05-15), one commit landed on main:
bd981a0This merge would have triggered another
_release-please-auto-merge.ymlrun (~22 hours ago), adding at least one more failure to the streak that began in early May.Root Cause (Persisting)
All gh-aw compiled workflows remain at v0.68.3 while the gh-aw-actions runtime has advanced to v0.74.2:
repo-health-audit.lock.ymllink-checker.lock.ymlagentics-maintenance.yml_release-please-auto-merge.ymlFix
Run
gh-aw-pin-refreshwithoperation: upgradeto recompile all gh-aw lock files at the current CLI version. Prior tracking: #312, #318.