Repository navigation
Conversation
Deploying patchling with
|
| 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An unpublished Patchling JavaScript version enters the npm packaging step after the existing test matrix, benchmark, and version checks pass for the
mainpush. 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 usenext.The package owner can register the GitHub Actions trusted publisher on npm for
255BITS/patchling/ci.yml/ environmentnpm, 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.