Find a way to pin workflow/action versions

[JonnyOThan]

Since workflows and actions call each other, it makes this difficult. We may need to have them check out the .github directory somewhere locally at the pinned ref and operate on local paths.

While I’d like to be able to support mods that don’t have kspbuildtools as a submodule, I think I’d also be ok with requiring that if you wanted to pin the workflow versions.

But all the major actions out there support pinning for reusable workflows - how do they do it? Do we just create a branch for each release and replace all the refs…?

[Twinki14]

I'd suggest separating them into different repositories,

KSPModdingLibs/actions for all re-usable actions
KSPModdingLibs/workflows for all re-usable workflows

Whenever you cut a release in those repositories, write a workflow that updates a major version tag with the release. I can help with this if needed.

That's how for example actions have @v3, so you would have @KSPModdingLibs/actions/[email protected] or @KSPModdingLibs/actions/publish-spacedock@v3

[drewcassidy]

https://github.com/dariocurr/checkout-called this is worth looking at.