Nathan Rajlich
32ac8e73fd
* Fix Biome lint violations and add Biome CI check Biome was not configured to respect .gitignore, so ~92% of the 13,355 reported diagnostics came from gitignored build artifacts. Enable VCS integration (useIgnoreFile), apply safe auto-fixes across the repo, fix the remaining mechanical errors by hand, downgrade judgment-call a11y / dangerouslySetInnerHTML rules to warnings, and add a 'biome ci' job to the Lint workflow so violations block PRs going forward. * Use an empty changeset (no behavior change, no release needed)
tarballs
Static Vercel project that builds and serves preview tarballs for every public package in packages/*.
For each public package, scripts/pack.ts:
- 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). - Runs
pnpm packand writes the result topublic/<escaped-name>.tgz. - Restores the original
package.jsonand 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.