Repository navigation
Commit f3f275c
committed
0.1.2
0.1.1 cannot be released. Rerunning a tag-triggered workflow checks out the
workflow file as it was at that tag, and v0.1.1 predates the tarball-check fix,
so it fails at the same step no matter what lands on main.
Releasing a new version is cleaner than rewriting the tag. 0.1.1 is skipped on
npm, which costs nothing.1 parent 81d6875 commit f3f275c
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
0 commit comments