Repository navigation
Fix
compare-actions.sh now flags a tag mismatch as outdated even when the SHAs coincide. Previously a pin like @<sha> # v1 against a repo whose latest release is v1.0.0 was reported as Up to date: (v1) because the floating v1 tag currently tracked v1.0.0's commit — the label never got refreshed in the auto-update PR.
This release also auto-bootstraps: existing consumers pinned as # v1 will now see the action open a PR to refresh the comment to # v1.0.1 on next run.
Technical
compare-actions.sh: treatcurrent_tag != latest_tagas outdated when both are non-empty, even when SHAs match. Pins without a#comment are unaffected.- Added three bats cases covering the fix and regression-guarding the existing up-to-date behavior.
Upgrading
For repos pinning @<sha> # v1: nothing to do — the next scheduled run will open an auto-update PR rewriting to @<new-sha> # v1.0.1.
For repos pinning by exact tag @<sha> # v1.0.0: same mechanism will advance to v1.0.1 as before.
See v1.0.0 release notes for full action usage.