Repository navigation
ci: publish preview releases with pkg.pr.new - #35
Conversation
Every push to main and every pull request now builds og-tester and publishes it to pkg.pr.new, so a fix can be installed from a commit sha before it ships to npm — without consuming a version number on the registry the way a snapshot publish would. The bundling smoke check from the release workflow runs here too, so a preview tarball can never ship a dist that still imports the private @og-tester/core workspace package. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a GitHub Actions workflow for preview releases on ChangesPreview release automation
Estimated code review effort: 2 (Simple) | ~10 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
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. A rabbit checks the bundle bright Comment |
commit: |
Description
There is currently no way to hand someone an unreleased build of the CLI. Metadata bugs are site-shaped — they need the reporter's own URL, their own headers, their own crawler behaviour — so "does
mainfix it?" today means asking them to clone and build the monorepo, or burning a real npm version on a snapshot just to produce a tarball.This adds
.github/workflows/preview-release.yml. Every push tomainand every pull request buildsog-testerand publishes it to pkg.pr.new, which serves the tarball from its own CDN and never touches the npm registry:A bot comment with the install line lands on each PR automatically. The changesets release flow is untouched.
Notes on the shape of it:
pull_requestpluspushonmainonly, so a PR branch does not run the job twiceog-tester, matchingrelease.yml, sowebstays out of it@og-tester/corebundling smoke check fromrelease.ymlruns here too — a preview tarball that still imports the private workspace package would be broken on install, and this catches it on the PR rather than at release timerelease.ymlif: github.repository_owner == 'PunGrumpy'so forks don't try to publishAdapted from
millionco/react-doctor.Verification
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 check — it repeats the build and smoke check that
release.ymlruns on every push tomaintoday.🤖 Generated with Claude Code
Summary by CodeRabbit