Skip to content

devops: publish npm packages under a pending dist-tag, promote them once live - #43979

Merged
Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
pavelfeldman:npm-pending-tags
Nov 6, 2026
Merged

Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
pavelfeldman:npm-pending-tags

Conversation

@pavelfeldman

Copy link
Copy Markdown
Member

Summary

  • publish_all_packages.sh publishes every package under <tag>-pending (next-pending, beta-pending, latest-pending) without waiting, as before devops: publish npm packages in dependency order and wait for them to go live #43933, and writes npm-publish.json, which publish_release.yml uploads.
  • New promote_release.yml runs after each publish run (or by hand with its run ID). It waits up to 5 hours for all packages to go live, installs them together, and moves <tag> over OIDC. It does not move a tag back to an older version.

npm makes a package live only after processing it. That usually takes under 3 minutes, but playwright-core took 55m19s in the 11-05 and 11-06 nightlies and 110m35s for 1.65.0. #43933 gave up after 15 minutes, so the 11-06 nightly published only playwright-core.

Before merging

  • On npmjs.com, add a trusted publisher for promote_release.yml to each public package with Allow npm dist-tag on (publishing can stay off). Without it, packages stay on <tag>-pending and <tag> stops moving.
  • OIDC npm dist-tag needs npm 11.21.0 or later, so the workflow installs npm@11.21.1 (the runner has 11.20.0).
  • Release branches keep publishing straight to beta until they pick this up. The promote job skips their runs, which have no npm-publish.json.

Not tested end to end: the promote path only runs against the real registry.

…nce live

npm makes a package live only after it processes it: usually within 3 minutes,
but playwright-core took 55 minutes in the 11-05 and 11-06 nightlies and 110
minutes for 1.65.0. Publish every package under <tag>-pending without waiting,
as before microsoft#43933, and move <tag> in a separate workflow once all of them are
live, using OIDC dist-tag permission.
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Test results for "tests 1"

23615 passed, 705 skipped


Merge workflow run.

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Test results for "MCP"

5194 passed, 616 skipped


Merge workflow run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants