Repository navigation
fix(sentry): stop reporting expected notFound/redirect as errors - #1310
sentry[bot] wants to merge 3 commits into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tanstack-com | 9382fa5 | Commit Preview URL Branch Preview URL |
Nov 04 2026, 02:09 AM |
|
|
Updated this against current main and replaced the property checks with Router’s isNotFound/isRedirect helpers. An actual redirect() result is a Response with options, so the old isRedirect === true check missed it. The regression uses real notFound()/redirect() values, keeps ordinary errors and HTTP 500 responses reportable, and checks that BYOK headers are still removed. Current server initialization settings are preserved. The full pnpm test suite and commit hooks passed: 550 unit tests passed with 4 skipped, 2269 chat tests passed, and 20 desktop tests passed with 1 skipped, plus type and lint checks. New CI is running on 3c6e2b5. The server instrumentation change still needs the required team review before merge. |
|
Updated this against current main so the Sentry fix can move forward without losing the newer privacy and stale-page recovery behavior. The required maintainer review still applies.
|
Filter expected Router notFound and redirect signals from Sentry while keeping real errors reportable. Uses Router’s isNotFound/isRedirect guards, including actual redirect Response values, and preserves the existing BYOK/privacy redaction, stale-page recovery and third-party script filters.
Fixes TANSTACK-COM-4QS
Originally generated by Sentry, updated through repository maintenance.