Skip to content

ci: Dispatch the sentry-docs @sentry/api bump on each release - #155

Merged
BYK merged 1 commit into
mainfrom
ci/dispatch-sentry-docs-bump
Nov 14, 2026
Merged

BYK merged 1 commit into
mainfrom
ci/dispatch-sentry-docs-bump

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Adds .github/workflows/bump-sentry-docs.yml. When a release is published, it dispatches sentry-docs' Bump @sentry/api workflow, so the docs pin the new version right away instead of waiting for the next hourly run.

  • It dispatches by file name (bump-api-schema-sha.yml, ref master). The cascade removed in ci: Remove the Cascade to sentry-docs workflow #154 dispatched by display name and broke when feat(api-docs): Build the API reference from @sentry/api/docs sentry-docs#20679 renamed the workflow.
  • It mints a token from the existing SENTRY_API_SCHEMA_UPDATER_* app, scoped to getsentry/sentry-docs with only actions: write, using the same pinned create-github-app-token action as before. The job's GITHUB_TOKEN has no permissions.
  • release: published fires for these releases. getsentry/publish creates them with the sentry-release-bot app token, not GITHUB_TOKEN, and the same trigger already runs on sentry-python's craft releases.
  • .craft.yml runs the npm target before github, so the version is already on npm when the release is published and the bump can install it.
  • The file has no repo-specific logic, so it can move to getsentry/sentry with the package. There it needs a guard for api@ tags.

via @BYK.

--

View Session [Sentry]

Each published release now dispatches sentry-docs' Bump @sentry/api
workflow by file name (bump-api-schema-sha.yml), so the docs pick up a
new version right away instead of at the next hourly run. The removed
cascade dispatched by display name and broke when that name changed.
@BYK
BYK merged commit ab538b9 into main Nov 14, 2026
11 checks passed
@BYK
BYK deleted the ci/dispatch-sentry-docs-bump branch November 14, 2026 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant