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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,7 @@ All notable changes to ContextForge will be documented in this file.
4
4
5
5
## Unreleased
6
6
7
-
- No unreleased changes tracked yet.
8
-
- The `0.1.0` entry below reflects the prepared release contents. GitHub Release creation and npm publish still happen only after the maintainer dispatches the release workflow successfully.
7
+
- Release automation now retries npm version verification for several minutes after publish so registry propagation delays do not immediately fail the workflow.
Copy file name to clipboardExpand all lines: docs/maintainers/npm-publish-guide.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,8 @@ If trusted publishing is not available yet:
30
30
31
31
The workflow will then publish using token auth instead of trusted publishing.
32
32
33
+
After a successful publish response, the workflow also retries npm visibility checks for a short window so normal registry propagation delays do not immediately mark the release as failed.
34
+
33
35
For the first live public release, keep these workflow inputs:
? 'npm registry still reports the package as not found'
392
+
: `npm registry returned version "${classification.actualVersion??'unknown'}"`;
393
+
console.log(
394
+
`${reason} is waiting for npm registry propagation: ${notFoundHint} for ${packageIdentifier} (attempt ${attempt}/${NPM_PUBLISH_VERIFY_MAX_ATTEMPTS}). Retrying in ${delaySeconds}s.`,
0 commit comments