We call it "Continuous Releases" too.
With pkg.pr.new, each of your commits and pull requests will trigger an instant preview release without publishing anything to NPM. This enables users to access features and bug-fixes without the need to wait for release cycles using npm or pull request merges.
- π Instant Builds
- π No Need for NPM Access
- π οΈ GitHub Workflows Friendly
- π¦οΈ No Configuration
- π© Single Command
- βοΈ Pull Request Comments
- π₯ Check Runs
pkg.pr.new won't publish anything to NPM; instead, it leverages its own URLs, which are npm-compatible.
npm i https://pkg.pr.new/tinylibs/tinybench/tinybench@a832a55
# npm i https://pkg.pr.new/${owner}/${repo}/${package}@{commit}
It is aiming to reduce the number of these comments :)
This was fixed in #18. Can we release that fix?
These are some of the projects and companies using pkg.pr.new:
Feel free to add your project or company here to join the pkg.pr.new family :)
First install the GitHub Application.
Important
Make sure it's installed on the repository before trying to publish a package.
After installing on your repository, you can run npx pkg-pr-new publish
in your workflows and then you have continuous releases!
npm install --save-dev pkg-pr-new # or `npx pkg-pr-new publish`
For workspaces and monorepos:
npx pkg-pr-new publish './packages/A' './packages/B' # or `npx pkg-pr-new publish './packages/*'`
Important
Make sure the pkg-pr-new command runs only once in a defined workflow (that's part of how it avoids spam)! So instead of multiple times running pkg-pr-new for each workspace package, the command should be run one time for all the desired packages using the pattern above.
For templates (experimental):
Note
With templates, pkg.pr.new will generate Stackblitz instances for the given directories with the new built packages.
npx pkg-pr-new publish './packages/A' --template './examples/*'
By default, pkg.pr.new will generate a template called "default" which includes each built package in the dependencies. This can be disabled with --no-template
.
For shorter urls, --compact
can be useful:
npx pkg-pr-new publish --compact './packages/A' './packages/B'
--compact
requires your package to be a valid (published) package on npm with a specifiedrepository
field in the package.json! See this. pkg.pr.new is case sensitive, if the GitHub owner isPuruVJ
, the package.jsonrepository
field should not havepuruvj
.
With --compact
:
npm i https://pkg.pr.new/tinybench@a832a55
Without --compact
:
npm i https://pkg.pr.new/tinylibs/tinybench/tinybench@a832a55
You can control publishing comments with --comment
:
npx pkg-pr-new publish --comment=update # default
Using --comment=update
, pkg.pr.new would generate one initial comment and then edit it in the following commits.
With --comment=create
, each commit would generate a comment for itself, useful for triggering workflows, like workflow execution using maintainer comments.
And --comment=off
would turn off comments for maintainers who prefer minimal pull requests.
For repositories with many packages, comments might get too long. In that case, you can use --only-templates
to only show templates.
pkg.pr.new uses npm pack --json
under the hood, in case you face issues, you can also use the --pnpm
flag so it starts using pnpm pack
. This is not necessary in most cases.
pkg.pr.new is not available in your local environment and it only works in workflows.
name: Publish Any Commit
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- run: corepack enable
- uses: actions/setup-node@v4
with:
node-version: 20
cache: "pnpm"
- name: Install dependencies
run: pnpm install
- name: Build
run: pnpm build
- run: pnpx pkg-pr-new publish
name: Publish Approved Pull Requests
on:
pull_request_review:
types: [submitted]
jobs:
approved:
if: github.event.review.state == 'APPROVED'
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- run: corepack enable
- uses: actions/setup-node@v4
with:
node-version: 20
cache: "pnpm"
- name: Install dependencies
run: pnpm install
- run: pnpx pkg-pr-new publish
on:
pull_request:
push:
branches:
- '**'
tags:
- '!**'
As noted in #140, workflows run on tags too, that's not an issue at all, but in case users would like to avoid duplicate publishes.
Releasing approved pull requests is the recommended way of having continuous releases. This ensures users always install approved and safe packages.
Publishing is only available in workflows and it supports any workflow trigger event, more information here.