You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 78e9601
Browse filesBrowse the repository at this point in the historyBrowse files
For example, when the packages are at `0.21.0`, commit the release fix and tag
247
+
that commit:
248
+
249
+
```sh
250
+
git tag -a 'v0.21.0+retry.1' -m 'Retry 0.21.0 publication.'
251
+
git push origin 'refs/tags/v0.21.0+retry.1'
252
+
```
253
+
254
+
The retry suffix belongs only in the Git tag, not in `package.json`. A `-1`
255
+
suffix is a distinct prerelease version, not a retry. Tag and package versions
256
+
are checked before dependency installation and the full CI jobs; retries still
257
+
run the normal release checks.
258
+
259
+
Retries publish only package versions that are still missing from npm. They
260
+
cannot replace an already-published version. If an earlier attempt partially
261
+
published the release and you changed its package contents, bump the version
262
+
instead of combining different contents under the same version.
263
+
235
264
For implementation history, use the design archive at `platform/meta/design-docs/README.md`. Its proposals explain earlier decisions; the source and current guides define the supported behavior.
0 commit comments