Skip to content

Commit bb44d98

Browse files
committed
docs: explain interrupted release marker recovery
1 parent 6468471 commit bb44d98

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎CONTRIBUTING.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,8 +119,8 @@ still requires registry access unless the dependencies are cached. Publishing re
119119
If core publication succeeds but a later package fails, run `pnpm release:publish` to finish the
120120
release. It skips versions already published and commits the development marker once every package
121121
succeeds. Plain `npm publish` cannot retry an already-published core version.
122-
If every upload succeeds but Git refuses the development-marker commit, fix the Git error and
123-
run `pnpm release:mark-dev` to finish any interrupted version synchronization, then commit the
122+
If every upload succeeds but development-marker synchronization or its Git commit fails, fix the
123+
reported error and run `pnpm release:mark-dev` to finish any interrupted version synchronization, then commit the
124124
changed public manifests and `server.json` before pushing. No package needs republishing.
125125

126126
Use `npm pack` to build and validate a development-version package locally. The normal npm and

0 commit comments

Comments
 (0)