Skip to content

Conversation

@andreiborza
Copy link
Member

Our e2e tests started breaking around the 1.142.x release of tanstack router, we ended up hard-pinning the version to 1.141.8.

The failures revealed a real behavioral change of matches tanstack router returns when attempting to match a non-existing route.

Previously the matches would be an empty array, but we now get a __root__ match.

The fix involves checking if the last match is __root__ and falling back to url for sentry.source attributes.

Closes: #18672

…utes

Our e2e tests started breaking around the `1.142.x` release of tanstack router,
we ended up hard-pinning the version to `1.141.8`.

The failures revealed a real behavioral change of matches tanstack router
returns when attempting to match a non-existing route.

Previously the matches would be an empty array, but we now get a `__root__`
match.

The fix involves checking if the last match is `__root__` and falling back to
`url` for `sentry.source` attributes.

Closes: #18672
@andreiborza andreiborza merged commit 5901e70 into develop Jan 8, 2026
119 of 120 checks passed
@andreiborza andreiborza deleted the ab/unpin-tanstack-router branch January 8, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix e2e tests failing for tanstack router 1.42.x

3 participants