Skip to content

docs: remove outdated/misleading warning #13484

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 2, 2025

Conversation

connorads
Copy link
Contributor

@connorads connorads commented Apr 23, 2025

DESCRIBE YOUR PR

As per getsentry/sentry-javascript#15439 (comment) this warning is no longer needed as of 9.13.0 where Cloudflare/Vercel (edge) support was added. Not entirely sure if there are other platforms that are still not supported will leave that one with you.

Screen Shot 2025-04-23 at 2 34 40 PM

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • None: Not urgent, can wait up to 1 week+

SLA

  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

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.

Copy link

vercel bot commented Apr 23, 2025

@connorads is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.

@connorads connorads marked this pull request as ready for review April 23, 2025 13:39
Copy link

vercel bot commented May 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sentry-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 1, 2025 9:36pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
changelog ⬜️ Ignored (Inspect) Visit Preview May 1, 2025 9:36pm
develop-docs ⬜️ Ignored (Inspect) Visit Preview May 1, 2025 9:36pm

Copy link
Contributor

@sfanahata sfanahata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like the right change based on the linked info. I don't think we changed any other platforms for this, @chargome?

@chargome chargome merged commit b62f9e3 into getsentry:master May 2, 2025
15 checks passed
codyde added a commit that referenced this pull request May 5, 2025
* 'master' of https://github.com/getsentry/sentry-docs:
  Fix small typo (#13570)
  Update trace explorer doc for GA (#13560)
  feat(cloudflare): Add jsonc instructions for sourcemaps upload (#13572)
  fix(apple): Missing semicolons in objc config snippets (#13578)
  feat(godot): Enriching events with scene tree data (#13531)
  feat(apple): Troubleshooting for subclass error (#13509)
  Make the API Design doc a bit more consistent (#13511)
  docs(js): Remove outdated/misleading warning (#13484)
  Refine SDK behavior docs for logs to make buffering more clear (#13573)
  fix(spike protection): correct floor calculation explanation (#13556)
  ref(docs): rm session health from early adopter (#13571)
  Bump API schema to 8c0365cd (#13564)
  Updating MCP docs with Video + Claude steps  (#13563)
@github-actions github-actions bot locked and limited conversation to collaborators May 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants