Merge branch 'master' into antonpirker/develop/startpage

Author: antonpirker

.github/workflows/lint-404s.yml

@@ -25,7 +25,7 @@ jobs:
               - 'platform-includes/**'
             dev-docs:
               - 'develop-docs/**'
-      - uses: oven-sh/setup-bun@v1
+      - uses: oven-sh/setup-bun@v2
         with:
           bun-version: latest
 

apps/changelog/package.json

@@ -18,7 +18,7 @@
     "seed": "node prisma/seed/seed.mjs"
   },
   "dependencies": {
-    "@auth/prisma-adapter": "^1.2.0",
+    "@auth/prisma-adapter": "^2.7.4",
     "@google-cloud/storage": "^7.7.0",
     "@prisma/client": "^5.8.1",
     "@radix-ui/react-icons": "^1.3.2",

apps/changelog/src/server/actions/changelog.ts

@@ -76,7 +76,6 @@ export async function createChangelog(
   if (!session) {
     return unauthorizedPayload;
   }
-  console.log({formData});
   const categories = formData.getAll('categories');
   await prismaClient.category.createMany({
     data: categories.map(category => ({name: category as string})),

develop-docs/api-server/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: API Server
-description: Documentation of the monolith, the hearth of Sentry. The backend of our application.
+description: Documentation of the monolith, the heart of Sentry. The backend of our application.
 sidebar_order: 50
 ---
 

develop-docs/engineering-practices/rust.mdx

@@ -7,7 +7,7 @@ sidebar_order: 40
 ## Getting Started
 
 - A quick introduction into the Syntax for first-timers:
-  [A half-hour to learn Rust](https://fasterthanli.me/blog/2020/a-half-hour-to-learn-rust/)
+  [A half-hour to learn Rust](https://fasterthanli.me/articles/a-half-hour-to-learn-rust)
 - The Rust Book, comprehensively documenting the language:
   [The Rust Programming Language](https://doc.rust-lang.org/book/)
 - [The Async Book](https://rust-lang.github.io/async-book/)

develop-docs/frontend/index.mdx

@@ -4,7 +4,7 @@ description: How we write frontend code at Sentry.
 sidebar_order: 60
 ---
 
-This guide specifically focussed on the [Sentry](https://github.com/getsentry/sentry) and [Getsentry](https://github.com/getsentry/getsentry) codebases. It assumes you are using the eslint rules outlined by [eslint-config-sentry](https://github.com/getsentry/eslint-config-sentry); hence code style enforced by these linting rules will not be discussed here.
+This guide specifically focuses on the frontend part of the [Sentry](https://github.com/getsentry/sentry) and [Getsentry](https://github.com/getsentry/getsentry) codebases. It assumes you are using the eslint rules outlined by [eslint-config-sentry](https://github.com/getsentry/eslint-config-sentry); hence code style enforced by these linting rules will not be discussed here.
 
 ## Directory structure
 

docs/platforms/dotnet/common/tracing/instrumentation/custom-instrumentation/caches-module.mdx

@@ -6,7 +6,7 @@ description: "Learn how to manually instrument your code to use Sentry's Caches
 
 A cache can be used to speed up data retrieval, thereby improving application performance. Because instead of getting data from a potentially slow data layer, your application will be getting data from memory (in a best case scenario). Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking.
 
-Sentry offers a [cache-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/caches/) for getting an overview of your application's caches.
+Sentry offers a [cache-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) for getting an overview of your application's caches.
 
 To make it possible for Sentry to give you an overview of your cache performance, you'll need to create two spans - one indicating that something is being put into the cache, and a second one indicating that something is being fetched from the cache.
 
@@ -102,4 +102,4 @@ public class MyCachingService
 }
 ```
 
-You should now have the right spans in place. Head over to the [Cache dashboard](https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/) to see how your cache is performing.
+You should now have the right spans in place. Head over to the [Cache dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) to see how your cache is performing.

docs/platforms/go/common/tracing/instrumentation/caches-module.mdx

@@ -91,4 +91,4 @@ if parentSpan != nil {
 }
 ```
 
-You should now have the right spans in place. Head over to the [Cache dashboard](https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/) to see how your cache is performing.
+You should now have the right spans in place. Head over to the [Cache dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) to see how your cache is performing.

docs/platforms/java/common/tracing/instrumentation/custom-instrumentation/caches-module.mdx

@@ -5,7 +5,7 @@ description: "Learn how to manually instrument your code to use Sentry's Caches
 ---
 A cache can be used to speed up data retrieval, thereby improving application performance. Because instead of getting data from a potentially slow data layer, your application will be getting data from memory (in a best case scenario). Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking.
 
-Sentry offers a [cache-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/caches/). For now you can manually instrument your caching solution and use Sentry to get a look into how it is performing by following the setup instructions below. We might be adding integrations to do this automatically, please head over to [GitHub](https://github.com/getsentry/sentry-java) and let us know which caching solution you'd like us to support.
+Sentry offers a [cache-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/). For now you can manually instrument your caching solution and use Sentry to get a look into how it is performing by following the setup instructions below. We might be adding integrations to do this automatically, please head over to [GitHub](https://github.com/getsentry/sentry-java) and let us know which caching solution you'd like us to support.
 
 To make it possible for Sentry to give you an overview of your cache performance, you'll need to create two spans - one indicating that something is being put into the cache, and a second one indicating that something is being fetched from the cache.
 
@@ -15,7 +15,7 @@ For detailed information about which data can be set, see the [Cache Module Deve
 
 ## Manual Instrumentation
 
-For now you'll need to manually instrument the [Cache Module](https://sentry.io/orgredirect/organizations/:orgslug/insights/caches/) by following the steps below.
+For now you'll need to manually instrument the [Cache Module](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) by following the steps below.
 
 <PlatformSection supported={["java.spring", "java.spring-boot"]}>
 If you are using Spring caching, please take a look at our [proof of concept PR](https://github.com/getsentry/sentry-java/pull/3457) as it shows how to register a cache listener and report cache spans to Sentry.

docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/caches-module.mdx

@@ -26,7 +26,7 @@ supported:
 
 A cache can be used to speed up data retrieval, thereby improving application performance. Because instead of getting data from a potentially slow data layer, your application will be getting data from memory (in a best case scenario). Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking.
 
-Sentry offers a [cache-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/) that can be auto-instrumented using Sentry's Redis integration (more coming soon).
+Sentry offers a [cache-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) that can be auto-instrumented using Sentry's Redis integration (more coming soon).
 
 ## Instrumentation with Redis Clients
 
@@ -44,7 +44,7 @@ Sentry.init({
 
 ## Manual Instrumentation
 
-If you're using anything other than Sentry's Redis integration, you'll need to manually instrument the [Cache Module](https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/) by following the steps below.
+If you're using anything other than Sentry's Redis integration, you'll need to manually instrument the [Cache Module](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) by following the steps below.
 
 You'll need to create two spans - one indicating that something is being put into the cache, and a second one indicating that something is being fetched from the cache.
 
@@ -129,4 +129,4 @@ Sentry.startSpan(
 );
 ```
 
-You should now have the right spans in place. Head over to the [Cache dashboard](https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/) to see how your cache is performing.
+You should now have the right spans in place. Head over to the [Cache dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/caches/) to see how your cache is performing.