Commit d004b53
ci: add workflow_dispatch + --force npm upgrade so a failed publish can be retried
Two changes wrapped together because they unblock the same problem.
`npm install -g npm@latest` fails inside the publish job with
`Cannot find module 'promise-retry'` — a known npm self-upgrade bug
where the in-place install removes the running npm's own dependencies
mid-flight. Adding `--force` bypasses that broken state and lets the
install complete.
Re-running the failed workflow uses the workflow file from the original
triggering SHA, so a fix on `main` can't unblock the existing v0.1.1
publish that already failed. Adding a `workflow_dispatch` trigger with
a `publish_tag` input lets the publish job be triggered manually
against any tag: release-please is skipped, checkout uses the input
ref, and the publish job's `if:` condition is widened to allow
workflow_dispatch runs. Filename stays `release-please.yml` so npm
Trusted Publishing still matches.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 30ece9b commit d004b53
1 file changed
Lines changed: 11 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
6 | 12 | | |
7 | 13 | | |
8 | 14 | | |
| |||
12 | 18 | | |
13 | 19 | | |
14 | 20 | | |
| 21 | + | |
15 | 22 | | |
16 | 23 | | |
17 | 24 | | |
| |||
25 | 32 | | |
26 | 33 | | |
27 | 34 | | |
28 | | - | |
| 35 | + | |
29 | 36 | | |
30 | 37 | | |
31 | 38 | | |
32 | 39 | | |
33 | 40 | | |
34 | 41 | | |
35 | 42 | | |
| 43 | + | |
| 44 | + | |
36 | 45 | | |
37 | 46 | | |
38 | 47 | | |
| |||
48 | 57 | | |
49 | 58 | | |
50 | 59 | | |
51 | | - | |
| 60 | + | |
52 | 61 | | |
53 | 62 | | |
54 | 63 | | |
0 commit comments