Commit 168857f
committed
Make NPM_TOKEN optional for package release
Same as w3c/webref#1744 for browser-specs.
Classic tokens are no longer supported by npm. We may still want to run the
release script from a local machine using a fine-grained access token, but
these tokens expire after 90 days at most and are thus not suitable for our
release process.
I set up OpenID Connect between the `browser-specs` and `web-specs` packages
in npm and GitHub Actions and dropped the former `NPM_TOKEN` secret.
This update adjusts the release script not to fail if such a token cannot be
found. The call to `npmPublish` gets adjusted accordingly only to pass the
token if it exists.1 parent 5f42bd1 commit 168857f
2 files changed
+7
-9
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
37 | | - | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
73 | 73 | | |
74 | 74 | | |
75 | 75 | | |
76 | | - | |
77 | | - | |
78 | | - | |
| 76 | + | |
| 77 | + | |
79 | 78 | | |
80 | | - | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
81 | 84 | | |
82 | 85 | | |
83 | 86 | | |
| |||
127 | 130 | | |
128 | 131 | | |
129 | 132 | | |
130 | | - | |
131 | | - | |
132 | | - | |
133 | | - | |
134 | 133 | | |
135 | 134 | | |
136 | 135 | | |
| |||
0 commit comments