Open janhoy opened 2 months ago
I concur. I think we can have semver branches as needed with each action taking its own release path to version branches. I would need to double check but that is equivalent to GHA.
I agree that there should be versioning as per GHA.
That does not play well with multiple actions in the same repository; they must share the same version branches if the GHA version naming convention is to be followed.
If each action has its own set of branches, then automated checkers such as dependabot are unlikely to work, and it will be harder for projects to use the actions.
Now we use
apache/infrastructure-actions/pelican@main
. Should we start releasing versioned actions so that users are shielded from unintended breaks, and also that they can do controlled upgrades through e.g. dependabot?