Files
github-actions[bot] 6d3186e102 [codex] Fix preview tarball generated versions (#2044) (#2052)
* Fix preview tarball generated versions

* Skip docs smoke for skipped preview deployments

* Address tarball review comments

Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-05-20 17:03:58 -07:00
..

tarballs

Static Vercel project that builds and serves preview tarballs for every public package in packages/*.

For each public package, scripts/pack.ts:

  1. Rewrites the package version to <version>-<git-sha>, updates generated version files to match, and rewrites every workspace dependency to a tarball URL on the current Vercel deployment (https://$VERCEL_URL/<escaped-name>.tgz).
  2. Runs pnpm pack and writes the result to public/<escaped-name>.tgz.
  3. Restores the original package.json and generated version files.

It also generates a public/index.html that lists every published package alongside a copyable pnpm i … command, so the bare deployment URL is itself useful when shared.

The deployment serves the resulting *.tgz files at the root of the project URL — e.g. https://<deployment>.vercel.sh/workflow.tgz.

This is used for pre-release testing of vercel/workflow PRs by installing tarballs directly:

{
  "dependencies": {
    "workflow": "https://<deployment>.vercel.sh/workflow.tgz"
  }
}

The Vercel project must be configured to be publicly accessible (no Deployment Protection on previews or production) so that pnpm/npm can fetch tarball URLs from third-party projects. The smoke check (scripts/check-tarballs-smoke.mjs) verifies this on every deployment and fails loudly if the deployment is behind a login redirect.