⚠️ No Changeset found

Latest commit: 06afc0c

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.

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

📦 CLI Tarball Ready

The Vercel CLI tarball for this PR is now available!

Quick Test

You can test this PR's CLI directly by running:

npx https://vercel-osx47y1g2.vercel.sh/tarballs/vercel.tgz --help

Use in vercel.json

To use this CLI version in your project builds, add to your vercel.json:

{
  "build": {
    "env": {
      "VERCEL_CLI_VERSION": "vercel@https://vercel-osx47y1g2.vercel.sh/tarballs/vercel.tgz"
    }
  }
}

Python Runtime Wheel

A vercel-runtime wheel was also built for this PR.
To use in your Python project builds, also set this environment variable:

VERCEL_RUNTIME_PYTHON="vercel-runtime @ https://vercel-osx47y1g2.vercel.sh/tarballs/vercel_runtime-0.14.0.dev1776389677+06afc0c-py3-none-any.whl"

Python Workers Wheel

A vercel-workers wheel was also built for this PR.
To use in your Python project builds, also set this environment variable:

VERCEL_WORKERS_PYTHON="vercel-workers @ https://vercel-osx47y1g2.vercel.sh/tarballs/vercel_workers-0.1.0.dev1776389677+06afc0c-py3-none-any.whl"

Low Risk — Automated changeset version bumps + changelog updates for package releases.

• .changeset/*.md: deleted consumed changeset files after release
• packages/*/package.json: version bumps across multiple packages
• packages/*/CHANGELOG.md: added release notes for new versions

^{Assessed at 06afc0c.}

🧪 Unit Test Strategy

Comparing: 8ad520b → 06afc0c (view diff)

Strategy: Affected packages only

✅ Only testing packages that have been modified or depend on modified packages.

Results

• Unit tests: Only affected packages will run unit tests
• E2E tests: Running in parallel via E2E Tests workflow
• Type checks: Only affected packages will run type checks

This comment is automatically generated based on the affected testing strategy

Ignoring CI here because it already passed in #16006. I have to do some shenanigans to get npm publish working via GH Actions.