Tag v4.3.0 was updated after initial release — was this intentional?

[varunsh-coder]

Describe the bug

I noticed that the Git tag v4.3.0 for this repository was originally created pointing to commit 59b4418, but it appears to have been updated to point to d0834ad.
https://github.com/aws-actions/configure-aws-credentials/releases/tag/v4.3.0

Could you please clarify whether this change was intentional?
In general semantic release tags are expected to be immutable. Updates to previously published semantic release tags can lead to inconsistencies in builds and raise supply chain security concerns. If this update was expected, it would be helpful to confirm.

Thanks in advance!

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

A semantic release tag would not be changed after initial release

Current Behavior

Semantic release tag v4.3.0 was changed after initial creation to point to a different commit

Reproduction Steps

N/A

Possible Solution

No response

Additional Information/Context

No response

[kellertk]

Yes, it was intentional. The initial 4.3.0 release was broken for anyone not using a proxy. In order to prevent broken workflows, we moved 4.3.0 to a bug fixed commit. We then published 4.3.1 shortly thereafter so workflows could be automatically updated correctly.

[github-actions]

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.

[kellertk]

To make this a little clearer, I've updated the release notes for v4.3.0 to explain this. Thanks!