Skip to content

v4 tag in the wrong commit #1327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
EduardoFer opened this issue Apr 16, 2025 · 3 comments
Closed

v4 tag in the wrong commit #1327

EduardoFer opened this issue Apr 16, 2025 · 3 comments
Labels
documentation This is an issue with documentation needs-triage This issue still needs to be triaged

Comments

@EduardoFer
Copy link

Describe the issue

Hi,

Acording to the description in the tag v4 "This tag will always track the latest v4 release". If we check the commit hash we can see that the v4 points to the commit of the tag v4.0.2 instead of the v4.1.0.

Image

Can you please realocate the tag?

Thanks

@EduardoFer EduardoFer added documentation This is an issue with documentation needs-triage This issue still needs to be triaged labels Apr 16, 2025
@alikulka
Copy link
Contributor

Hello @EduardoFer,

As mentioned in the release notes for v4, this is the expected behavior. Releases of this action starting v4.0.3 and newer follow semantic versioning for tags. While using newer versions of this action, you need to specify the exact version tag.

For example,
uses: aws-actions/[email protected]

Copy link

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.

@EduardoFer
Copy link
Author

Hi,

Thanks for the info.

Regards,
Eduardo Fernandes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is an issue with documentation needs-triage This issue still needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants