craft(gh-pages): update, version "0.25.0"

Author: sentry-release-bot[bot]

.well-known/skills/index.json

@@ -7,18 +7,22 @@
         "SKILL.md",
         "references/api.md",
         "references/auth.md",
-        "references/dashboards.md",
-        "references/events.md",
-        "references/issues.md",
-        "references/logs.md",
-        "references/organizations.md",
-        "references/projects.md",
+        "references/cli.md",
+        "references/dashboard.md",
+        "references/event.md",
+        "references/init.md",
+        "references/issue.md",
+        "references/log.md",
+        "references/org.md",
+        "references/project.md",
         "references/release.md",
-        "references/setup.md",
+        "references/repo.md",
+        "references/schema.md",
         "references/sourcemap.md",
-        "references/teams.md",
-        "references/traces.md",
-        "references/trials.md"
+        "references/span.md",
+        "references/team.md",
+        "references/trace.md",
+        "references/trial.md"
       ]
     }
   ]

.well-known/skills/sentry-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sentry-cli
-version: 0.24.1
+version: 0.25.0
 description: Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
 requires:
   bins: ["sentry"]
@@ -103,6 +103,31 @@ sentry schema issues
 sentry schema "GET /api/0/organizations/{organization_id_or_slug}/issues/"
 ```
 
+#### Manage Releases
+
+```bash
+# Create a release — version must match Sentry.init({ release }) exactly
+sentry release create my-org/1.0.0 --project my-project
+
+# Associate commits via repository integration (needs local git checkout)
+sentry release set-commits my-org/1.0.0 --auto
+
+# Or read commits from local git history (no integration needed)
+sentry release set-commits my-org/1.0.0 --local
+
+# Mark the release as finalized
+sentry release finalize my-org/1.0.0
+
+# Record a production deploy
+sentry release deploy my-org/1.0.0 production
+```
+
+**Key details:**
+- The positional is `<org-slug>/<version>`. In `sentry release create sentry/1.0.0`, `sentry` is the org and `1.0.0` is the version — the slash separates org from version, it is not part of the version string.
+- The **version** must match the `release` value in `Sentry.init()`. If your SDK uses `"1.0.0"`, the command must use `org/1.0.0`.
+- `--auto` requires a Sentry repository integration (GitHub/GitLab/Bitbucket) **and** a local git checkout. It matches your `origin` remote against Sentry's repo list. Without a checkout, use `--local`.
+- With no flag, `set-commits` tries `--auto` first and falls back to `--local` on failure.
+
 #### Arbitrary API Access
 
 ```bash
@@ -193,38 +218,6 @@ sentry span list my-org/my-project/abc123def456...
 
 When querying the Events API (directly or via `sentry api`), valid dataset values are: `spans`, `transactions`, `logs`, `errors`, `discover`.
 
-### Release Workflow
-
-The `sentry release` command group manages Sentry releases for tracking deploys and associating commits with errors. A typical CI workflow:
-
-```bash
-# Create a release (version must match Sentry.init() release value)
-sentry release create my-org/1.0.0 --project my-project
-
-# Associate commits via repository integration (requires git checkout)
-sentry release set-commits my-org/1.0.0 --auto
-
-# Mark the release as finalized
-sentry release finalize my-org/1.0.0
-
-# Record a deploy
-sentry release deploy my-org/1.0.0 production
-```
-
-**Key details:**
-
-- The `org/version` positional is `<org-slug>/<version>`, NOT a version prefix. `sentry release create sentry/1.0.0` means org=`sentry`, version=`1.0.0`. This is how org is specified — not via `SENTRY_ORG`.
-- The release **version** (e.g., `1.0.0`) must match the `release` value in your `Sentry.init()` call. If your SDK uses bare semver, the release must be bare semver too.
-- `--auto` requires **both** a Sentry repository integration (GitHub/GitLab/Bitbucket) **and** a local git checkout. It lists repos from the API and matches against your local `origin` remote URL, then sends the HEAD commit SHA. Without a checkout, use `--local` instead.
-- When neither `--auto` nor `--local` is specified, the CLI tries `--auto` first and falls back to `--local` on failure.
-
-#### CI/CD Setup Notes
-
-- The `sentry` npm package requires **Node.js >= 22**. CI runners like `ubuntu-latest` ship Node.js 20 — add `actions/setup-node@v6` with `node-version: 22`.
-- If `SENTRY_AUTH_TOKEN` is scoped to a GitHub environment (e.g., `production`), set `environment: production` on the job.
-- A full git checkout (`fetch-depth: 0`) is needed for `--auto` to discover the remote URL and HEAD.
-- `set-commits --auto` has `continue-on-error` in most workflows because it requires a working repository integration. If the integration isn't configured, the step fails but the rest of the release workflow succeeds.
-
 ### Common Mistakes
 
 - **Wrong issue ID format**: Use `PROJECT-123` (short ID), not the numeric ID `123456789`. The short ID includes the project prefix.
@@ -283,7 +276,7 @@ Work with Sentry organizations
 - `sentry org list` — List organizations
 - `sentry org view <org>` — View details of an organization
 
-→ Full flags and examples: `references/organizations.md`
+→ Full flags and examples: `references/org.md`
 
 ### Project
 
@@ -294,36 +287,38 @@ Work with Sentry projects
 - `sentry project list <org/project>` — List projects
 - `sentry project view <org/project>` — View details of a project
 
-→ Full flags and examples: `references/projects.md`
+→ Full flags and examples: `references/project.md`
 
 ### Issue
 
 Manage Sentry issues
 
 - `sentry issue list <org/project>` — List issues in a project
+- `sentry issue events <issue>` — List events for a specific issue
 - `sentry issue explain <issue>` — Analyze an issue's root cause using Seer AI
 - `sentry issue plan <issue>` — Generate a solution plan using Seer AI
 - `sentry issue view <issue>` — View details of a specific issue
 
-→ Full flags and examples: `references/issues.md`
+→ Full flags and examples: `references/issue.md`
 
 ### Event
 
-View Sentry events
+View and list Sentry events
 
 - `sentry event view <org/project/event-id...>` — View details of a specific event
+- `sentry event list <issue>` — List events for an issue
 
-→ Full flags and examples: `references/events.md`
+→ Full flags and examples: `references/event.md`
 
-### Api
+### API
 
 Make an authenticated API request
 
 - `sentry api <endpoint>` — Make an authenticated API request
 
 → Full flags and examples: `references/api.md`
 
-### Cli
+### CLI
 
 CLI-related commands
 
@@ -332,7 +327,7 @@ CLI-related commands
 - `sentry cli setup` — Configure shell integration
 - `sentry cli upgrade <version>` — Update the Sentry CLI to the latest version
 
-→ Full flags and examples: `references/setup.md`
+→ Full flags and examples: `references/cli.md`
 
 ### Dashboard
 
@@ -345,7 +340,7 @@ Manage Sentry dashboards
 - `sentry dashboard widget edit <org/project/dashboard...>` — Edit a widget in a dashboard
 - `sentry dashboard widget delete <org/project/dashboard...>` — Delete a widget from a dashboard
 
-→ Full flags and examples: `references/dashboards.md`
+→ Full flags and examples: `references/dashboard.md`
 
 ### Release
 
@@ -369,15 +364,15 @@ Work with Sentry repositories
 
 - `sentry repo list <org/project>` — List repositories
 
-→ Full flags and examples: `references/teams.md`
+→ Full flags and examples: `references/repo.md`
 
 ### Team
 
 Work with Sentry teams
 
 - `sentry team list <org/project>` — List teams
 
-→ Full flags and examples: `references/teams.md`
+→ Full flags and examples: `references/team.md`
 
 ### Log
 
@@ -386,7 +381,7 @@ View Sentry logs
 - `sentry log list <org/project-or-trace-id...>` — List logs from a project
 - `sentry log view <org/project/log-id...>` — View details of one or more log entries
 
-→ Full flags and examples: `references/logs.md`
+→ Full flags and examples: `references/log.md`
 
 ### Sourcemap
 
@@ -404,7 +399,7 @@ List and view spans in projects or traces
 - `sentry span list <org/project/trace-id...>` — List spans in a project or trace
 - `sentry span view <trace-id/span-id...>` — View details of specific spans
 
-→ Full flags and examples: `references/traces.md`
+→ Full flags and examples: `references/span.md`
 
 ### Trace
 
@@ -414,7 +409,7 @@ View distributed traces
 - `sentry trace view <org/project/trace-id...>` — View details of a specific trace
 - `sentry trace logs <org/trace-id...>` — View logs associated with a trace
 
-→ Full flags and examples: `references/traces.md`
+→ Full flags and examples: `references/trace.md`
 
 ### Trial
 
@@ -423,23 +418,23 @@ Manage product trials
 - `sentry trial list <org>` — List product trials
 - `sentry trial start <name> <org>` — Start a product trial
 
-→ Full flags and examples: `references/trials.md`
+→ Full flags and examples: `references/trial.md`
 
 ### Init
 
 Initialize Sentry in your project (experimental)
 
 - `sentry init <target> <directory>` — Initialize Sentry in your project (experimental)
 
-→ Full flags and examples: `references/setup.md`
+→ Full flags and examples: `references/init.md`
 
 ### Schema
 
 Browse the Sentry API schema
 
 - `sentry schema <resource...>` — Browse the Sentry API schema
 
-→ Full flags and examples: `references/setup.md`
+→ Full flags and examples: `references/schema.md`
 
 ## Global Options
 

.well-known/skills/sentry-cli/references/api.md

@@ -1,13 +1,13 @@
 ---
 name: sentry-cli-api
-version: 0.24.1
-description: Make arbitrary Sentry API requests
+version: 0.25.0
+description: Make an authenticated API request
 requires:
   bins: ["sentry"]
   auth: true
 ---
 
-# API Command
+# API Commands
 
 Make an authenticated API request
 

.well-known/skills/sentry-cli/references/auth.md

@@ -1,13 +1,13 @@
 ---
 name: sentry-cli-auth
-version: 0.24.1
-description: Authenticate with Sentry via OAuth or API tokens
+version: 0.25.0
+description: Authenticate with Sentry
 requires:
   bins: ["sentry"]
   auth: true
 ---
 
-# Authentication Commands
+# Auth Commands
 
 Authenticate with Sentry
 

…nown/skills/sentry-cli/references/cli.md …nown/skills/sentry-cli/references/cli.mdpr-preview/pr-670/.well-known/skills/sentry-cli/references/cli.md renamed to .well-known/skills/sentry-cli/references/cli.md pr-preview/pr-670/.well-known/skills/sentry-cli/references/cli.md renamed to .well-known/skills/sentry-cli/references/cli.md

@@ -1,6 +1,6 @@
 ---
 name: sentry-cli-cli
-version: 0.25.0-dev.0
+version: 0.25.0
 description: CLI-related commands
 requires:
   bins: ["sentry"]

…kills/sentry-cli/references/dashboard.md …kills/sentry-cli/references/dashboard.mdpr-preview/pr-680/.well-known/skills/sentry-cli/references/dashboard.md renamed to .well-known/skills/sentry-cli/references/dashboard.md pr-preview/pr-680/.well-known/skills/sentry-cli/references/dashboard.md renamed to .well-known/skills/sentry-cli/references/dashboard.md

@@ -1,6 +1,6 @@
 ---
 name: sentry-cli-dashboard
-version: 0.25.0-dev.0
+version: 0.25.0
 description: Manage Sentry dashboards
 requires:
   bins: ["sentry"]