[next] Fix e2e tests with hardcoded build id#14886
Conversation
🦋 Changeset detectedLatest commit: 08a9e42 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📦 CLI Tarball ReadyThe Vercel CLI tarball for this PR is now available! Quick TestYou can test this PR's CLI directly by running: npx https://vercel-mdsmf0o7a.vercel.sh/tarballs/vercel.tgz --helpUse in vercel.jsonTo use this CLI version in your project builds, add to your {
"build": {
"env": {
"VERCEL_CLI_VERSION": "vercel@https://vercel-mdsmf0o7a.vercel.sh/tarballs/vercel.tgz"
}
}
} |
🧪 Unit Test StrategyComparing: Strategy: Code changed outside of a package - running all unit tests Affected packages - 40 (100%)
Results
This comment is automatically generated based on the affected testing strategy |
Since vercel/next.js#89325, the build id is overridden to a hardcoded string
build-TfctsWXpff2fKSwhen skew protection is enabled.https://github.com/vercel/next.js/blob/2521b8adc73957cf7dfc358bea3c461b04bcfa16/packages/next/src/build/index.ts#L906-L910
Update the e2e tests to use that instead.