Commit e546f9a
committed
s/v1.0.1.0.1.0.1/v1.0.1/ on the bandit-action pin comment
Dependabot nailed the SHA bump (67a458d really is v1.0.1) but garbled the
trailing comment into v1.0.1.0.1.0.1. It got tripped up because the old
line was already mislabeled: the comment said v1.0.1 while the pin sat on
the v1.0.0 commit. The action runs fine either way -- the pin is the SHA,
the comment is just for humans -- but a nonsense version tag is exactly
the kind of thing future-me squints at six months from now.
Checked the other eight pinned actions in the group against their upstream
tags while I was in here:
- every SHA matches the version its comment claims
- this bandit line was the only casualty
Comment only. No SHA changes.1 parent 69264e5 commit e546f9a
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
| 27 | + | |
28 | 28 | | |
29 | 29 | | |
0 commit comments