Commit fbe0d8e
authored
fix(cd): publish 13.0.0, and stop reporting success when nothing publishes (#537)
* chore(cd): log npm at verbose so OIDC failures explain themselves
The publish now fails with a bare ENEEDAUTH. npm's OIDC helper logs every failure path
at verbose, so at the default loglevel there is no way to tell a missing trusted
publisher from a permissions problem or a bad id_token:
log.verbose('oidc', `Failed token exchange request with body message: ...`)
log.verbose('oidc', 'Failed because token exchange was missing the token in the body')
log.silly('oidc', 'Skipped because incorrect permissions for id-token ...')
Raising the loglevel makes the next run state the reason instead of us inferring it.
* fix(cd): fail the publish step when nothing gets published
Re-running an old CD run went green having shipped nothing. A workflow re-run checks out
the run's original commit, where the manifests still carried the pre-release versions, so
`lerna version` declined with an EBEHIND warning and exited 0, and every package then
looked already published and was skipped.
The publish script now exits non-zero when it publishes no packages, so that state fails
loudly instead of reporting success.1 parent db7451b commit fbe0d8e
2 files changed
Lines changed: 17 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
61 | 65 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
0 commit comments