Philip Durbin 🚀 (Nov 19 2024 at 14:18): Philip Durbin 🚀 (Nov 19 2024 at 14:18):Does @v4 mean "the latest version 4" or does it mean the tag v1 per "we only match a literal release tag" in a comment by a GitHubber.
Philip Durbin 🚀 (Nov 19 2024 at 14:18):We're discussing this a bit here: https://github.com/IQSS/dataverse-frontend/pull/550#issuecomment-2485837059
Philip Durbin 🚀 (Nov 19 2024 at 14:24):Oh, nice. Edward Thomson already replied with this:
"actions authors need to make the updates to the "major version tag" themselves"
Philip Durbin 🚀 (Nov 20 2024 at 14:11):It's sort of crazy, how you can't know what @v4 means. It depends on the author of the action.
Philip Durbin 🚀 (Nov 20 2024 at 14:12):"> @ethomson thanks for getting back to us so fast! Does this mean that for any action we can't know if the author is making updates to the "major version tag" or not? We have to poke around?
I think that you do. And there's a few cases here: the author does this _always, and reliably_, the author never does this, or the author has a manual process to do this when they publish and maybe sometimes forgets.
I think that GitHub is pretty good about always updating the major version tag for their actions. (Hopefully automated, or at least tested; I honestly don't remember.) But me, personally, I'm in the latter camp and sometimes forget. :cry: " -- https://github.com/IQSS/dataverse-frontend/pull/550#issuecomment-2485965006
Philip Durbin 🚀 (Nov 21 2024 at 17:26):@Ceilyn Boyd this is the GitHub Actions "v4" vs "v4.1.7" discussion I was telling you about.
Last updated: Nov 01 2025 at 14:11 UTC