馃摑 Description
Hi there,
It looks like the v47 major tag was not moved/force-pushed to the latest v47.0.6 release commit.
For users relying on the floating major tag (uses: tj-actions/changed-files@v47) to automatically pick up the latest non-breaking patches, they are currently missing out on the updates included in v47.0.6 and are stuck on an older version.
Expected Behavior
The v47 tag should point to the exact same commit as the v47.0.6 tag.
Actual Behavior
The v47 tag is currently pointing to an older commit in the v47 lifecycle instead of the latest patch release.
馃挕 Suggested Action
Could you please update or force-push the v47 tag to the v47.0.6 commit?
Thank you for maintaining this awesome action!
馃摑 Description
Hi there,
It looks like the
v47major tag was not moved/force-pushed to the latestv47.0.6release commit.For users relying on the floating major tag (
uses: tj-actions/changed-files@v47) to automatically pick up the latest non-breaking patches, they are currently missing out on the updates included inv47.0.6and are stuck on an older version.Expected Behavior
The
v47tag should point to the exact same commit as thev47.0.6tag.Actual Behavior
The
v47tag is currently pointing to an older commit in the v47 lifecycle instead of the latest patch release.馃挕 Suggested Action
Could you please update or force-push the
v47tag to thev47.0.6commit?Thank you for maintaining this awesome action!