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 page loads on the changed logs guides. It also checks client errors on those guides. An issue escalates when those pages fail to load or client errors rise. Services: Mention PlanWhat changedJavaScript logs pages now render Consola setup steps. Node.js and Bun logs pages also render Winston setup steps. Nested Winston headings drop one level. RiskA broken include can fail render on every JavaScript logs page. The Winston heading change can break in-page anchors on pages that already include that snippet. Wrong platform matching can hide Winston on Node.js or Bun. It can also show Winston on browser guides. Intended effectThis is a documentation edit. Telemetry does not show whether the new Consola or Winston blocks render. Page-load volume only shows that the URLs still respond. The executor cannot mark this axis Regression watchClient errors are the symptom-class signal. Traces use a 0.3 sample rate. Error events do not. Do not divide error counts by span counts. Ignore Algolia fetch failures and recaptcha
Sampled sitewide pageload and navigation volume was 13200 spans in the same window. Use that volume to judge whether an error rise is traffic, not a new failure. Not observableWhether Consola setup HTML appears. Whether Winston setup HTML appears only on Node.js and Bun. LCP and INP metrics returned no values. JavaScript-logs-only error events could not be isolated from other JavaScript platform URLs. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
the branch is up to date. could you approve the pending workflows and authorize the Vercel preview when you review this? |
|
Deployment failed for project develop-docs with the following error: |
|
Deployment failed for project sentry-docs with the following error: |
|
Restricted the logger section to supported SDKs. Deno does not export the Consola reporter, and the shared Hono guide covers Deno too. The MDX and platform-selection checks pass; the rendered preview is still unverified |
DESCRIBE YOUR PR
Refs #19755
The shared JavaScript logs page mentions Consola but doesn't render its setup instructions. The existing Winston instructions are also missing from the Node.js and Bun logs pages.
This reuses the existing includes under a Logging Libraries section. The Logging Libraries section excludes Deno and the multi-runtime Hono guide because the Deno SDK does not export the Consola reporter. Winston remains limited to Node.js and Bun, whose SDKs export the transport. The separate Next.js page is unchanged. Winston's option headings now sit beneath its integration heading.
This is only the missing-instructions part of #19755. It does not change quickstarts, runtime metrics, or coverage for other server frameworks.
Validation:
Rendered-page verification is still pending. A fresh local docs-tree generation on Windows fails with
missing parent and grandparent: api, and Vercel requires team authorization. No successful browser verification or full build is claimed. The platform-selection helper was checked with Deno, Hono, Node.js, Bun and React; this is not a full-page test.AI assistance was used to prepare and check this change.
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
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.