ci: publish preview releases with pkg.pr.new

[PunGrumpy]

Description

Today there is no way to hand someone an unreleased build of the CLI. Reproducing a Docker diagnosis bug takes the reporter's own containers, so "can you check whether main fixes it?" currently means either asking them to clone and build the monorepo, or burning a real npm version on a snapshot publish just to get a tarball out.

This adds .github/workflows/preview-release.yml. Every push to main and every pull request builds @docker-doctor/cli and publishes it to pkg.pr.new, which serves the tarball from its own CDN and never touches the npm registry:

bun add https://pkg.pr.new/@docker-doctor/cli@<sha>

A bot comment with the install line lands on each PR automatically. Nothing about the changesets release flow changes.

Notes on the shape of it:

• pull_request plus push on main only, so a PR branch does not run the job twice
• build is filtered to @docker-doctor/cli, matching changeset:publish, so web and videos stay out of it — the generated skill/ directory is produced by that build, so the tarball carries it
• action pinning, the Bun cache step, and bun install copied from code-quality.yml
• if: github.repository_owner == 'PunGrumpy' so forks don't try to publish
• the publish step retries up to four times with backoff — pkg.pr.new returns transient 5xx often enough to matter

Adapted from millionco/react-doctor.

Related Issues

N/A — infrastructure, no issue behind it.

Checklist

• I've reviewed my code
• I've written tests — n/a, CI-only change
• I've generated a changeset file, if this changes a published package — n/a, no package source changes
• I've updated the docs, if necessary

Additional Notes

The pkg.pr.new GitHub App has to be installed on this repo before this merges, otherwise the publish step fails. No tokens or secrets needed beyond that. The run on this PR is the real verification — it exercises the same build path as code-quality.yml, which is green today.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docker-doctor	Ready	Preview	Sep 10, 2026 6:29pm UTC

[coderabbitai]

Warning

Review limit reached

Next included review available in 38 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: bae6300a-eb47-4acf-99ce-fee2f06df4d6

📥 Commits

Reviewing files that changed from the base of the PR and between 13b47a2 and 80b74f5.

📒 Files selected for processing (1)

• .github/workflows/preview-release.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 80b74f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

The latest Docker Doctor scan for this pull request. Learn more about Docker Doctor.

File	Status	Issues	Updated
Dockerfile	Error	1 error, 2 info	Sep 10, 2026 6:29pm UTC

Score: 84 / 100 · Good

3 issues

Dockerfile

• Dockerfile:2 Potential secret found in ENV: 'DB_PASSWORD'. no-secrets-in-env
• Dockerfile:1 No HEALTHCHECK instruction found. require-healthcheck
• Dockerfile:1 No LABEL metadata was found in this Dockerfile. require-labels

_{Scanned by Docker Doctor for commit 80b74f5.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@docker-doctor/cli@128

commit: 80b74f5