We classified this failure as environment_state because the failing task (tanstack-solid-start-e2e-basic:test:e2e--vite-preview) belongs to the solid-start E2E suite, while this PR exclusively modifies @tanstack/react-router. The test asserting window.SCRIPT_1 === true after client-side navigation is a solid-start script-injection concern with no connection to the Link re-render bail-out changes introduced here.
Self-Healing CI
Classification: Environment state
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The failing task is tanstack-solid-start-e2e-basic:test:e2e--vite-preview, which belongs to the solid-start E2E test suite.
The PR only touches @tanstack/react-router — specifically the useLinkProps hook and related Link re-render bail-out logic. The touched projects list confirms this: ["@tanstack/react-router"].
The failing test (tests/navigation.spec.ts:47) checks that window.SCRIPT_1 is true after client-side navigation to a scripts route in a solid-start app. This is a solid-start script-injection concern, completely unrelated to react-router's Link comparator changes.
Since the failing project is not in touched_projects, there is no code path connecting the PR's changes to this test failure.
The flakiness rate for this task is 0%, which rules out a transient/flaky classification.
With no overlap between the changed code and the failing test, and no flakiness history, the failure is a pre-existing environment or build-artifact issue in the solid-start E2E setup that exists independently of this PR.