Repository navigation
Conversation
|
@sansynx is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
|
The plan checks redirects on the three broken source-map URLs, sibling JavaScript source-map pages, and production errors. An issue escalates when those URLs still fail to redirect or error volume rises above the measured band. Services: Mention PlanWhat changedRequests to RiskA bad redirect map can send valid JavaScript guide source-map pages to the wrong URL. A middleware fault can fail every request on both ships. Intended effectThe new behavior is a 301 on those three paths.
Those three logs all occurred at 2026-10-04T06:45:03Z to 2026-10-04T06:45:04Z. After deploy, Regression watchA broken redirect table can widen to valid JavaScript guide source-map pages or fail middleware for every request. Watch errors first. Then watch redirect volume and sibling source-map pages.
If error volume rises, check whether valid Not observableHTTP 404 and 301 status codes for the three broken URLs are not in traces. A 24h query for |
coolguyzone
left a comment
There was a problem hiding this comment.
LGTM, thanks so much for fixing this @sansynx!
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
DESCRIBE YOUR PR
Fixes #17865
Fixes #17859
Fixes #17858
The reported source maps links use Django, PHP, and Rails project names as JavaScript guide names. All three return 404. This redirects those exact URLs to the JavaScript source maps guide, which returns 200
The three cases share one fix, so they are grouped here. Regression tests exercise the middleware response and check that the destination does not redirect again. All 82 middleware and redirect-tooling tests pass
This repairs the docs URLs only, not the code that generates links in the Sentry application. Vercel preview review is still pending
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES