Commit e5500ef
authored
ci(release): publish to npm via trusted publishing, idempotent loop (#105)
* ci(release): publish to npm via trusted publishing (OIDC)
The publish job failed with npm E404 because it published unauthenticated
(no NODE_AUTH_TOKEN; setup-node's placeholder token). Switch to npm Trusted
Publishing instead of a long-lived token:
- upgrade npm to >= 11.5.1 (OIDC support) after setup-node
- drop NODE_AUTH_TOKEN and the --provenance flag; with the GitHub Actions
OIDC environment (id-token: write) npm authenticates via the per-package
Trusted Publisher on npmjs.com and generates provenance automatically
Requires a Trusted Publisher configured on npmjs.com for each @pleaseai/code*
package (repo pleaseai/code-intelligence, workflow file release-please.yml).
* ci(release): make npm publish idempotent (skip already-published versions)
A partial publish left @pleaseai/code-darwin-arm64@0.1.14 on npm while the
other 7 packages stayed at 0.1.13. Re-running aborted on the first package
with 'cannot publish over previous version', never reaching the missing ones.
Check npm view per package and publish only versions not yet present.1 parent 44b1b40 commit e5500ef
1 file changed
Lines changed: 24 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
82 | 92 | | |
83 | 93 | | |
84 | | - | |
85 | | - | |
86 | | - | |
87 | | - | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
0 commit comments