You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.
In order to reduce the burden of workflow dependency management for users, it is standard practice for action maintainers to provide a major version ref:
The maintainers have neglected the critical task of moving the major version ref tag at each release. The v1 tag is still at d6b3a6f (v1.1.4), which means those who use this ref in their workflows are stuck using the outdated version 1.1.4 of the action instead of version 1.3.1 as expected.
Since this update was missed for three releases in a row, it seems likely that it will be forgotten again in future releases. In order to avoid that, I recommend either producing a formal release procedure document for the maintainers to follow, or even better setting up an automated system.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Background
In order to reduce the burden of workflow dependency management for users, it is standard practice for action maintainers to provide a major version ref:
https://docs.github.com/actions/sharing-automations/creating-actions/about-custom-actions#good-practices-for-release-management
Such a major version ref is provided for this action:
https://github.com/github/setup-licensed/releases/tag/v1
Problem
The maintainers have neglected the critical task of moving the major version ref tag at each release. The
v1
tag is still at d6b3a6f (v1.1.4
), which means those who use this ref in their workflows are stuck using the outdated version 1.1.4 of the action instead of version 1.3.1 as expected.Resolution
Please move the
v1
tag tov1.3.1
:Additional context
Since this update was missed for three releases in a row, it seems likely that it will be forgotten again in future releases. In order to avoid that, I recommend either producing a formal release procedure document for the maintainers to follow, or even better setting up an automated system.
The text was updated successfully, but these errors were encountered: