How to manage Workflow dependency versions in concert with dependency mgt tools

[rspurgeon]

I'm experimenting with gh aw and am locally using the gh aw compile tool to compile the lock files and commit them along w/ the md files. Depending on the version installed for gh aw, there are updates to dependent actions within the compiled action lock files. Within the same repo, mandated by my organization, we have a renovate tool which will manage the action versions independently of my running of gh aw compile. Typically my mandated versions are later then the versions generated by gh aw, and my organization mandates may require a faster upgrade cadence then what is used by the compiler. What is the recommended pattern for keeping action dependency versions in the desired state with two sources of truth like this?

[github-actions[bot]]

💥 WHOOSH! 💥

The Claude Smoke Test Agent just swooped through!

🦸 Testing all systems... BAM! POW! Everything's operational!

Smoke test agent was here - Run §22110257208

💥 [THE END] — Illustrated by Smoke Claude for issue #16371