Conversation
🔄 Action Pin Diff
|
| Action | Tag | Expected SHA | Pinned SHA |
|---|---|---|---|
actions/checkout |
v7.0.0 |
tag not found | de0fac2 |
vvoland
added a commit
that referenced
this pull request
Apr 17, 2026
When a pin-only result (SHA unchanged) also has a tag/SHA mismatch, it was shown in both the "⚠️ Tag / SHA Mismatch" table and the "📌 Pinned (digest unchanged)" table. The pin-only table displayed the incorrect tag (e.g. v7.0.0) next to the digest as if it were valid, which is misleading. Now results that match a mismatch entry are excluded from the pin-only section entirely — the mismatch table already surfaces the problem clearly. Reproduces the issue from PR #7 where only the version comment changed (v6.0.2 → v7.0.0) but the SHA stayed the same. Signed-off-by: Paweł Gronowski <git@grono.dev>
vvoland
added a commit
that referenced
this pull request
Apr 17, 2026
When a pin-only result (SHA unchanged) also has a tag/SHA mismatch, it was shown in both the "⚠️ Tag / SHA Mismatch" table and the "📌 Pinned (digest unchanged)" table. The pin-only table displayed the incorrect tag (e.g. v7.0.0) next to the digest as if it were valid, which is misleading. Now results that match a mismatch entry are excluded from the pin-only section entirely — the mismatch table already surfaces the problem clearly. Reproduces the issue from PR #7 where only the version comment changed (v6.0.2 → v7.0.0) but the SHA stayed the same. Signed-off-by: Paweł Gronowski <git@grono.dev>
vvoland
force-pushed
the
update
branch
4 times, most recently
from
e395f90 to
72c76e0
Compare
Previously, when resolveRefSHA returned 404 or 422 (tag doesn't exist), the error was silently swallowed and no mismatch was reported. Now 404/422 responses are treated as "tag not found" and produce a mismatch with an empty expectSHA. Server errors (5xx) are still silently skipped since they're transient. The render handles empty expectSHA by showing "*tag not found*" in the Expected SHA column of the mismatch table. Signed-off-by: Paweł Gronowski <git@grono.dev>
Add `fail-on-mismatch` input (default: true) that causes the action to exit non-zero when mismatches are detected. The comment is still posted before failing so the PR author sees what's wrong. Previously mismatches were only logged as warnings and the workflow always succeeded, making it easy to miss incorrect version comments. Signed-off-by: Paweł Gronowski <git@grono.dev>
vvoland
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.