feat: use v1 for the time being

[v1v]

As long as we don't have a way to centralise those inter-dependencies somehow let's use v1.

I'd probably say if we use v1 then all the relevant dependencies should be using v1, if we use v1.9.1 then all the dependencies should point to that particular version regardless

[v1v]

I'm not sure how to proceed here, there will be always a version below of the one we hav.e released.

[reakaleek]

I'm not sure how to proceed here, there will be always a version below of the one we hav.e released.

I don't think it matters if there are no changes to the related actions.

But generally, it would be a 2 step release.

first, release the inner action with the changes
secondly, create a new release with the updated version

[v1v]

first, release the inner action with the changes
secondly, create a new release with the updated version

That will cause a recurrent bump and dependabot will create PRs over and over:

• build(deps): bump the github-actions group across 6 directories with 1 update #82

I'm not sure how to proceed here

[reakaleek]

first, release the inner action with the changes
secondly, create a new release with the updated version

That will cause a recurrent bump and dependabot will create PRs over and over:

• build(deps): bump the github-actions group across 6 directories with 1 update #82

I'm not sure how to proceed here

Yes, this is true. But if you have already released two releases with changes to the inner and outer dependency, the last update by Dependabot doesn't affect their behavior.

Hence, we can just merge it and don't do a release until we need or want to