Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Clarify That GitHub Actions Don't Automatically Understand Semantic Versioning #17071
Comments
Kurt-von-Laven
added
the
content
github-actions
bot
added
the
triage
This comment was marked as spam.
This comment was marked as spam.
ramyaparimi
added
actions
|
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert |
|
This is a gentle bump for the docs team that this issue is waiting for technical review. |
|
It's correct that actions does not "understand' semantic versioning, but we're clear in our suggestions that action authors publish semantic versioned tags. Can you suggest some language that aligns these two things? Perhaps we should iterate in a pull request. |
ramyaparimi
added
SME reviewed
|
@Kurt-von-Laven Thank you for opening this issue. You or anyone else is welcome to open a PR as per the SME review |
ramyaparimi
removed
the
waiting for review
|
Thank you for the pointer to that doc! I found a related one previously that didn't mention authors publish all tags, but not that very clear one. I opened a PR; open to suggestions. |
|
@ramyaparimi, would you be able to reopen this issue since the associated pull request was accidentally closed? |
|
@Kurt-von-Laven I see that this issue is already open, only the associated PR is closed. Would you like to create a new PR with a fix for this issue? |
|
Wow, clearly I needed more coffee |
and others
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsuses
What part(s) of the article would you like to see updated?
This section can be read to imply that GitHub Actions understands semantic versioning, but it does not. In order for users to specify a major action version, the action maintainer has to tag it themselves. It would be good to clarify that tagging a major version only works if the maintainer chooses to support it. In my personal opinion, the risks of being broken by a bad release outweigh the benefits of always using the latest version of an action (at a specified major version). I would suggest pinning a specific version and using Dependabot to keep up-to-date instead.
Additional information
No response
The text was updated successfully, but these errors were encountered: