Merge remote-tracking branch 'origin/master' into armcknight/feat(use…

…r-feedback)/cocoa-docs

.env.example

@@ -3,5 +3,5 @@
 # warning: variables prefixed with NEXT_PUBLIC_ will be made available to client-side code
 # be careful not to expose sensitive data (in this case your Algolia admin key)
 
-NEXT_PUBLIC_ALGOLIA_APP_ID=OOK48W9UCL
-NEXT_PUBLIC_ALGOLIA_SEARCH_KEY=ca98597f559459c216891b75989832f8
+NEXT_PUBLIC_ALGOLIA_APP_ID=
+NEXT_PUBLIC_ALGOLIA_SEARCH_KEY=

.eslintrc.js

@@ -1,24 +1,10 @@
-/* eslint-env node */
-/* eslint import/no-nodejs-modules:0 */
-
 module.exports = {
   extends: ['sentry-docs', 'plugin:@next/next/recommended'],
   globals: {
-    jest: true,
     Atomics: 'readonly',
     SharedArrayBuffer: 'readonly',
   },
   rules: {
     'import/no-nodejs-modules': 'off',
   },
-  overrides: [
-    {
-      files: ['*.ts', '*.tsx'],
-      rules: {
-        // Reach is vendored into gatsby. They have their own webpack
-        // resolution for it which this eslint plugin can't seem to detect
-        'import/no-unresolved': ['error', {ignore: ['@reach']}],
-      },
-    },
-  ],
 };

.github/CODEOWNERS

@@ -36,7 +36,7 @@
 # /src/docs/product/discover-queries/ @getsentry/visibility
 # /src/docs/product/performance/ @getsentry/visibility
 
-# /src/docs/product/cli/dif/ @getsentry/owners-native
+# /src/docs/cli/dif.mdx @getsentry/owners-native
 
 # /.github/labels.yml @getsentry/open-source
 # /.github/workflows/react-to-product-owners-yml-changes.yml @getsentry/open-source
@@ -51,4 +51,6 @@
 # /src/platforms/javascript/common/session-replay/                  @getsentry/replay @getsentry/replay-sdk-web
 # /src/wizard/javascript/replay-onboarding/                         @getsentry/replay @getsentry/replay-sdk-web
 
+# /src/docs/product/dev-toolbar/                                    @getsentry/replay
+
 # ###### End Replays #######

.github/ISSUE_TEMPLATE/issue-content-01-sdks.yml

@@ -0,0 +1,61 @@
+name: "📝 SDK Documentation"
+labels: ["Type: Content", "SDKs"]
+description: Missing, incorrect, or unclear documentation of SDKs.
+body:
+  - type: markdown
+    attributes:
+      value: |-
+        Is the documentation issue something you know how to fix? Consider contributing to Open Source by opening a PR to fix it instead!
+  - type: dropdown
+    id: area
+    attributes:
+      label: SDK
+      description: Which SDK documentation are we talking about?
+      options:
+        - Android SDK
+        - Apple SDK
+        - Dart SDK
+        - Elixir SDK
+        - Flutter SDK
+        - Go SDK
+        - Java SDK
+        - JavaScript SDK
+        - Kotlin Multiplatform SDK
+        - Native SDK
+        - .NET SDK
+        - PHP SDK
+        - PowerShell SDK
+        - Python SDK
+        - React Native SDK
+        - Ruby SDK
+        - Rust SDK
+        - Unity SDK
+        - Unreal Engine SDK
+        - Sentry CLI
+        - All JavaScript SDKs
+        - All Backend SDKs
+        - All Mobile SDKs
+        - All Gaming SDKs
+        - All SDKs
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What were you looking for/trying to do/expecting?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Suggested Solution
+      description: If you have an idea on how we can solve this, please share.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |-
+        ## Thanks 🙏
+        Check our [triage docs](https://open.sentry.io/triage/) for what to expect next.

.github/ISSUE_TEMPLATE/issue-content.yml → .github/ISSUE_TEMPLATE/issue-content-02-product.yml

@@ -1,26 +1,16 @@
-name: "📝 Docs Content"
-labels: "Type: Content"
-description: Missing, incorrect, unclear documentation or code samples.
+name: "📝 Product Documentation"
+labels: ["Type: Content", "Product"]
+description: Missing, incorrect, or unclear documentation of product features.
 body:
   - type: markdown
     attributes:
       value: |-
         Is the documentation issue something you know how to fix? Consider contributing to Open Source by opening a PR to fix it instead!
-  - type: dropdown
-    id: area
-    attributes:
-      label: Core or SDK?
-      description: What part of the Sentry documentation are we talking about?
-      options:
-        - Core Sentry product
-        - Platform/SDK
-    validations:
-      required: true
   - type: input
     id: area-specific
     attributes:
       label: Which part? Which one?
-      description: Which area of the core Sentry product, or which platform/SDK?
+      description: Which area of the core Sentry product?
     validations:
       required: true
   - type: textarea
@@ -42,5 +32,3 @@ body:
       value: |-
         ## Thanks 🙏
         Check our [triage docs](https://open.sentry.io/triage/) for what to expect next.
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/issue-content-03-develop.yml

@@ -0,0 +1,38 @@
+name: "📝 Documentation on develop.sentry.dev"
+labels: ["Type: Content", "Develop"]
+description: Missing, incorrect, or unclear developer documentation.
+body:
+  - type: markdown
+    attributes:
+      value: |-
+        Is the documentation issue something you know how to fix? Consider contributing to Open Source by opening a PR to fix it instead!
+  - type: input
+    id: area-specific
+    attributes:
+      label: Which section?
+      description: Which section of the developer documentation needs to be updated?
+    validations:
+      required: true
+  - type: input
+    id: page-url
+    attributes:
+      label: Page URL
+      description: Please provide the URL of the page which should be changed (if applicable).
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What were you looking for/trying to do/expecting?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Suggested Solution
+      description: If you have an idea on how we can solve this, please share.
+  - type: markdown
+    attributes:
+      value: |-
+        ## Thanks 🙏
+        Check our [triage docs](https://open.sentry.io/triage/) for what to expect next.
+  

.github/labels.yml

@@ -17,6 +17,16 @@
   color: F6F6F8
   description: Pull requests that update a dependency file
 
+# Issue types
+- name: 'Type: Content'
+  color: FBCA04
+- name: 'Type: Platform'
+  color: 1D76DB
+
+#
+- name: 'Develop'
+  color: F6F6F8
+
 # Impacts
 - name: 'Impact: Large'
   color: C83852
@@ -32,6 +42,8 @@
   color: '584774'
 - name: 'Platform: Capacitor'
   color: '584774'
+- name: 'Platform: CLI'
+  color: '584774'
 - name: 'Platform: Cocoa'
   color: '584774'
 - name: 'Platform: Cordova'
@@ -40,14 +52,20 @@
   color: '584774'
 - name: 'Platform: Elixir'
   color: '584774'
+- name: 'Platform: Flutter'
+  color: '584774'
 - name: 'Platform: Go'
   color: '584774'
+- name: 'Platform: iOS'
+  color: '584774'
 - name: 'Platform: Java'
   color: '584774'
 - name: 'Platform: JavaScript'
   color: '584774'
 - name: 'Platform: KMP'
   color: '584774'
+- name: 'Platform: Native'
+  color: '584774'
 - name: 'Platform: PHP'
   color: '584774'
 - name: 'Platform: Python'
@@ -67,6 +85,7 @@
 - name: 'Platform: Xamarin'
   color: '584774'
 
+
 # Waiting for Labels
 - name: 'Waiting for: Support'
   color: '8D5494'
@@ -217,16 +236,36 @@
 - name: 'Team: Web Frontend'
   color: 8D5494
   description: team-web-sdk-frontend
+- name: 'Team: Web Frontend SDKs'
+  color: 8D5494
+  description: team-web-sdk-frontend
 - name: 'Team: Web SDK Backend'
   color: 8D5494
   description: team-web-sdk-backend
+- name: 'Team: Web Backend SDKs'
+  color: 8D5494
+  description: team-web-sdk-backend
 - name: 'Team: Workflow'
   color: 8D5494
+- name: 'All SDKs'
+  color: 1D76DB
+- name: 'SDKs'
+  color: 1D76DB
+- name: 'Develop'
+  color: 8D5494
+- name: 'Do not merge'
+  color: 8D5494
+- name: 'Improvement'
+  color: 8D5494
+- name: 'Launch 🚀'
+  color: 8D5494
+- name: 'Product'
+  color: 8D5494
 
 # Miscellaneous
 - name: API Docs
   color: 649B42
-- name: bug
+- name: Bug
   color: F6F6F8
 - name: Common content
   color: B0E299
@@ -279,3 +318,11 @@
   color: F6F6F8
 - name: release health
   color: F6F6F8
+- name: submodules
+  color: F6F6F8
+- name: '404'
+  color: F6F6F8
+- name: darkmode
+  color: F6F6F8
+- name: github_actions
+  color: F6F6F8

.github/workflows/algolia-index.yml

@@ -25,7 +25,7 @@ jobs:
               - 'develop-docs/**'
       - uses: oven-sh/setup-bun@v2
         with:
-          bun-version: latest
+          bun-version: '1.1.34'
 
       - uses: actions/cache@v4
         id: cache

.github/workflows/bump-api-schema-sha.yml

@@ -12,13 +12,19 @@ jobs:
     name: 'Bump API Schema SHA'
     steps:
       - uses: actions/[email protected]
+      - name: Get auth token
+        id: token
+        uses: actions/create-github-app-token@5d869da34e18e7287c1daad50e0b8ea0f506ce69 # v1.11.0
+        with:
+          app-id: ${{ vars.SENTRY_INTERNAL_APP_ID }}
+          private-key: ${{ secrets.SENTRY_INTERNAL_APP_PRIVATE_KEY }}
       - name: 'Bump API Schema SHA'
         shell: bash
         env:
           # An elevated token is necessary because with plain github.token
           # GitHub does not recursively call workflows, which means CI does not
           # kick off for the PR we're about to create.
-          GITHUB_TOKEN: ${{ secrets.GH_RELEASE_PAT }}
+          GITHUB_TOKEN: ${{ steps.token.outputs.token }}
         run: |
           set -euo pipefail
 

.github/workflows/enforce-version-convention.yml

@@ -0,0 +1,22 @@
+name: Enforce Version Conventions
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    branches: [master]
+
+jobs:
+  check-version-convention:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Run script for checking conventions
+        run: bun scripts/check-version-conventions.ts