An action I am using, uses by default actions/cache@v1.
When I configured Dependabot, it created a PR with an update to actions/[email protected].
I saw on the page of actions/cache, the version in the example code is v2 and not the latest release v2.1.3.
Should I update to v2.1.3 or is there a specific reason to use v2 instead, as showed in the example code ?
aleks-ivanov
All 5 comments
We update the v2 tag to point to the latest release, so currently v2 is the same as v2.1.3. We recommend using v2 so you are always using the latest version.
dhadka
on 6 Jan 2021
We update the
v2tag to point to the latest release, so currentlyv2is the same asv2.1.3. We recommend usingv2so you are always using the latest version.
Does that apply automatically to all actions or do you do it for yourself manually ?
aleks-ivanov
on 6 Jan 2021
Yes, when we change the tag all uses of actions/cache@v2 in any workflow will automatically start using the new version.
(Edited for clairty)
dhadka
on 6 Jan 2021
(I realized there's a second possible interpretation of your last question. This way of versioning, where we have a "major version" tag such as @v2 that points to the latest patch version, is something we do manually for the official GitHub actions. This is not automatically done for all actions.)
dhadka
on 6 Jan 2021
Thank you!
aleks-ivanov
on 6 Jan 2021
Related issues
s-weigand
路
5Comments
binhxn
路
3Comments
thisismydesign
路
4Comments
gladhorn
路
4Comments
Lyeeedar
路
5Comments
Most helpful comment
(I realized there's a second possible interpretation of your last question. This way of versioning, where we have a "major version" tag such as
@v2that points to the latest patch version, is something we do manually for the official GitHub actions. This is not automatically done for all actions.)