Skip to content

Re-enable e2e tests on all PRs#15008

Merged
jeffsee55 merged 10 commits intomainfrom
jeffsee55/e2e-tests-on-prs
Feb 12, 2026
Merged

Re-enable e2e tests on all PRs#15008
jeffsee55 merged 10 commits intomainfrom
jeffsee55/e2e-tests-on-prs

Conversation

@jeffsee55
Copy link
Copy Markdown
Contributor

@jeffsee55 jeffsee55 commented Feb 11, 2026 •
edited by vercel bot
Loading

Summary

This reverts the experiment that restricted e2e tests to only Version Packages PRs. E2E tests now run on every pull request again.

  • Removed the check-trigger job that gated e2e tests
  • E2E tests run on all PRs instead of only Version Packages PRs or those with the run-e2e-tests label
  • Updated PR comment text to reflect the change

🤖 Generated with Claude Code

Note

Low Risk Change

This PR removes conditional gating on e2e tests to run them on all PRs, which is a CI workflow change with no security or business logic impact.

  • Removed check-trigger job that gated e2e tests to specific PRs
  • E2E tests now run unconditionally on all pull requests
  • Updated PR comment text to reflect new e2e test behavior

Risk assessment for commit 22d4f6a.

@jeffsee55 @claude
Re-enable e2e tests on all PRs
c94c3d9 
Remove the check-trigger job that restricted e2e tests to only Version Packages PRs or those with the run-e2e-tests label. E2E tests now run on every pull request again, matching the previous pattern.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@jeffsee55 jeffsee55 requested review from a team and ijjk as code owners February 11, 2026 19:58
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Feb 11, 2026 •
edited
Loading

⚠️ No Changeset found

Latest commit: 22d4f6a

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

ijjk
ijjk reviewed Feb 11, 2026
View reviewed changes
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 11, 2026 •
edited
Loading

📦 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-c5fr9qibd.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-c5fr9qibd.vercel.sh/tarballs/vercel.tgz"
    }
  }
}

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 11, 2026 •
edited
Loading

🧪 Unit Test Strategy

Comparing: a960cf2 → 22d4f6a (view diff)

Strategy: Code changed outside of a package - running all unit tests

⚠️ All unit tests will run because global code changes could impact all packages.

Affected packages - 15 (38%)
  1. @vercel/build-utils
  2. @vercel/client
  3. @vercel/firewall
  4. @vercel/fs-detectors
  5. @vercel/go
  6. @vercel/hydrogen
  7. @vercel/next
  8. @vercel/node
  9. @vercel/python
  10. @vercel/remix-builder
  11. @vercel/ruby
  12. @vercel/rust
  13. @vercel/static-build
  14. examples
  15. vercel
Unaffected packages - 25 (63%)
  1. @vercel-internals/get-package-json
  2. @vercel/backends
  3. @vercel/cervel
  4. @vercel/cli-auth
  5. @vercel/config
  6. @vercel/detect-agent
  7. @vercel/edge
  8. @vercel/elysia
  9. @vercel/error-utils
  10. @vercel/express
  11. @vercel/fastify
  12. @vercel/frameworks
  13. @vercel/functions
  14. @vercel/gatsby-plugin-vercel-builder
  15. @vercel/h3
  16. @vercel/hono
  17. @vercel/koa
  18. @vercel/nestjs
  19. @vercel/oidc
  20. @vercel/oidc-aws-credentials-provider
  21. @vercel/python-analysis
  22. @vercel/redwood
  23. @vercel/related-projects
  24. @vercel/routing-utils
  25. @vercel/static-config

Results

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

This comment is automatically generated based on the affected testing strategy

@jeffsee55 jeffsee55 enabled auto-merge (squash) February 11, 2026 22:36
@mehulkar mehulkar mentioned this pull request Feb 12, 2026
Merged
@jeffsee55 jeffsee55 merged commit 886d918 into main Feb 12, 2026
190 checks passed
@jeffsee55 jeffsee55 deleted the jeffsee55/e2e-tests-on-prs branch February 12, 2026 06:30
mehulkar added a commit that referenced this pull request Feb 12, 2026
@mehulkar @cursoragent
[cli] move builders to peer dependencies (try 2) (#15023)
127547d 
Merged in #14763, reverted in
#15022.

Re-submitting and running e2e tests now via label. e2e tests are coming
back by default to PRs in #15008

- Moves builders to peerDependencies and tells pnpm that they're
optional dependencies. With this config, `pnpm` will not bundle them
into the publishd `vercel` CLI, but they will be in the manifest.
- Add a feature to the `resolveBuilders` function that reads the
peerDependencies section of package.json at runtime and installs that
correct version of the builder. It stores this builder in a local cache
(`.vercel/builders`) so it only has to get them from the registry once.

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ijjk ijjk ijjk approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jeffsee55 @ijjk