Skip to content

Publish new Patchling npm versions on main merges - #18

Draft
mikkel wants to merge 1 commit into
mainfrom
ci/publish-npm-on-main
Draft

mikkel wants to merge 1 commit into
mainfrom
ci/publish-npm-on-main

Conversation

@mikkel

@mikkel mikkel commented Nov 18, 2026

Copy link
Copy Markdown
Member

An unpublished Patchling JavaScript version enters the npm packaging step after the existing test matrix, benchmark, and version checks pass for the main push. An already published version skips upload. The publish job downloads the tarball built from the tested revision and checks the registry again before publishing. Prereleases use next.

The package owner can register the GitHub Actions trusted publisher on npm for 255BITS / patchling / ci.yml / environment npm, with direct publishing allowed. The workflow uses a GitHub-hosted runner and is ready for that registration. No npm token is needed.

Verified read-only registry checks against existing 0.3.2 and an absent version, shell syntax, and npm pack --dry-run.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying patchling with  Cloudflare Pages  Cloudflare Pages

Latest commit: d4ebcc6
Status: ✅  Deploy successful!
Preview URL: https://c0e4358b.patchling.pages.dev
Branch Preview URL: https://ci-publish-npm-on-main.patchling.pages.dev

View logs

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.

1 participant