Problem
Our raycast/extensions is using raycast/github-actions/setup-git@master and raycast/github-actions/git-commit@master. But in raycast/github-actions, the raycast/github-actions/git-commit is using the raycast/github-actions/setup-git@v1.16.0. Which is not consistent.
Solution
See https://github.com/actions/toolkit/blob/main/docs/action-versioning.md.
The solution in the official documentation is to use a v1 tag to manage the major version. But it requires you update the tag with --force on every update.
A better solution is to use a branch called v1 and keep our code in this branch.
Benefits
We don't need to update all versions for raycast/extensions and raycast/github-actions on every update. And it's easier to keep your usages both in raycast/extensions and raycast/github-actions consistent.
Problem
Our
raycast/extensionsis usingraycast/github-actions/setup-git@masterandraycast/github-actions/git-commit@master. But inraycast/github-actions, theraycast/github-actions/git-commitis using theraycast/github-actions/setup-git@v1.16.0. Which is not consistent.Solution
See https://github.com/actions/toolkit/blob/main/docs/action-versioning.md.
The solution in the official documentation is to use a
v1tag to manage the major version. But it requires you update the tag with--forceon every update.A better solution is to use a branch called
v1and keep our code in this branch.Benefits
We don't need to update all versions for
raycast/extensionsandraycast/github-actionson every update. And it's easier to keep your usages both inraycast/extensionsandraycast/github-actionsconsistent.