fix casing Github -> GitHub (#15739)
Fixed casing from "Github" to "GitHub" in the index.mdx file.
Documentation Changelog
Track recent updates to Sentry docs
chore(docs): delete github deployment gate (#15742)
Removed GitHub deployment gate from Sentry documentation to streamline the process and improve clarity for users.
feat(develop/span-first): Add implementation guidelines page (#15717)
Added "Implementation Guidelines" page to Spans SDK develop section for guidance on implementing span-first and documenting decisions/questions. Update encouraged.
docs(self-hosted): move 'Configuration' to its' own section (#15600)
Moved 'Configuration' to a separate section in self-hosted docs to better explain system functionality beyond just setup.
feat: add guides for more otel collector use cases (#15680)
Added guides for utilizing the otel collector with AWS CloudWatch, Kafka, Nginx, syslog, and Windows Events for common infra/applications.
Update docs (#15701)
Updated data forwarding section for Splunk in Sentry docs.
feat: Doc on introducing breaking changes to SDKs (#15647)
Added a page to guide discussions on introducing breaking changes in SDKs, including examples, user impact, and tips for minimizing friction.
docs(dotnet): fix Blazor WebAssembly example (#15731)
Fixed missing methods `UseSentry` and `AddSentry` in Blazor WebAssembly example due to missing `<ImplicitUsings>enable` in `.csproj` or disabled implicit usings from `Microsoft.NET.Sdk.BlazorWebAssembly` Project-SDK.
feat(crons): Add missing .NET docs (#15697)
Added missing .NET documentation for upsert and Heartbeat in dotnet.mdx file.
df docs (#15704)
Added data forwarding page under /organizations/integrations/data-forwarding in Sentry docs.
feat: Add docs about vercel drains via vercel marketplace integration (#15730)
Added documentation for log/trace drains via Vercel Marketplace integration in Sentry, detailed in index.mdx and vercel.mdx files.
docs(tanstackstart-react): Add source maps quickstart instructions (#15709)
Added source maps quickstart instructions for Tanstack Start React SDK in the documentation.
docs(sourceMaps): Add `filesToDeleteAfterUpload` when source maps are enabled (#15609)
Added `filesToDeleteAfterUpload` option in snippets with enabled source maps, now presented as a warning in Sentry docs.
fix(apple): Enhance GraphQL operation tracking documentation (#15716)
Enhanced documentation for GraphQL operation tracking in files graphql-operation-tracking.mdx, http-client-errors.mdx, and options.mdx.
docs(js): update Solid quick start guide (#15644)
Updated Solid Quick Start guide in Sentry docs.
feat(spans): Document trace attachments (#15705)
Added documentation for trace attachments in spans to provide more context and visibility into distributed tracing data.
ref(metrics): add metric options for PHP (#15715)
Added metric options for PHP in the Sentry documentation.
feat(metrics): move PHP to list of supported SDKs (#15712)
Added PHP to list of supported SDKs in Sentry documentation.
feat(metrics): add documentation for metrics for laravel/symfony (#15694)
Added documentation for metrics for Laravel/Symfony due to different flushing behaviors compared to regular SDK, ensuring accurate usage.
update uptime ips url (#15722)
Updated the URL for uptime IPs in the ip-ranges.mdx file.
Showing the 20 most recent updates. View the full content dashboard or subscribe to the RSS feed.
- Full Content Dashboard - View all Sentry content (blog, videos, docs, changelog)
- RSS Feed - Subscribe to doc updates in your RSS reader
- JSON API - Programmatically access changelog data
The changelog updates automatically throughout the day. Summaries are generated by AI to provide quick, user-friendly insights into each update from the getsentry/sentry-docs repository.
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").