Failed

fix: do not collapse explicit-undefined params when stabilising link options view more

8bd81fcd

Self-Healing CI

Classification: Environment state

We identified the failure in tanstack-vue-start-e2e-basic:test:e2e--vite-ssr--shard-4-of-4 as an environment state issue unrelated to this PR. The error is a missing export in a stale e2e/e2e-utils dist artifact, and the failing project is not touched by our changes to @tanstack/react-router. Rebuilding the e2e-utils package in the CI environment should resolve this.

An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.

The failing task tanstack-vue-start-e2e-basic:test:e2e--vite-ssr--shard-4-of-4 is not related to this PR's changes for the following reasons:

Unrelated project: The PR only touches @tanstack/react-router, but the failing task belongs to the tanstack-vue-start-e2e-basic project — a Vue project that was not modified.
Stale build artifact: The error is a SyntaxError in a compiled dist file (e2e/e2e-utils/dist/esm/index.js) trying to import an export toRuntimePath that does not exist in the compiled to-runtime-path.js. This indicates a mismatch between the dist artifact and the current source, consistent with a stale or incorrectly built environment artifact.
Zero flakiness rate: The task has a flakiness rate of 0%, ruling out a flaky test classification.
No similar failures on other branches: The similar-task-failure-detector found no matching failures on other branches, suggesting this is an isolated environment issue rather than a widespread regression.
No connection to diff: There is no code path in this PR's diff that could have caused the e2e-utils dist file to lose the toRuntimePath export. The failure would resolve by rebuilding the e2e-utils package in the CI environment.