Skip to content

fix(release): tag and release even when npm is slow to serve a package #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Madraka merged 1 commit into from
Oct 21, 2026
Merged

fix(release): tag and release even when npm is slow to serve a package #66

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion scripts/publish-ci.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,11 @@ if (missing.length) {
}
for (let i = 0; i < 30 && (await unpublished(pkgs, onNpm)).length; i++)
await new Promise((r) => setTimeout(r, 10_000));
// `npm publish` succeeded for each, so the registry has them; it can take longer than five
// minutes to serve one (0.3.8, 0.3.10). That must not keep the tag and the release back.
const left = await unpublished(pkgs, onNpm);
if (left.length) throw new Error(`npm does not serve yet: ${left.map((p) => p.name).join(", ")}`);
if (left.length)
console.warn(`npm does not serve yet: ${left.map((p) => p.name).join(", ")}; tagging anyway`);
} else console.log(`npm already has every package at ${version}`);

const tag = `v${version}`;
Expand Down
Loading