Repository navigation
ci: Remove the Cascade to sentry-docs workflow - #154
Merged
Merged
Conversation
sentry-docs now builds its API reference from @sentry/api/docs and pins the package with its own hourly Bump @sentry/api workflow (getsentry/sentry-docs#20679). It no longer reads this repo's spec, and the workflow it dispatched, Bump API Schema SHA, no longer exists under that name.
sentry-junior
Bot
requested review from
BYK,
MathurAditya724 and
betegon
as code owners
November 13, 2026 23:23
BYK
approved these changes
Nov 13, 2026
2 tasks done
BYK
pushed a commit
that referenced
this pull request
Nov 14, 2026
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 #154 dispatched by display name and broke when getsentry/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. <!-- junior-request-attribution:start --> via @BYK. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:agent%3A69da19b385017e68b7f9eace56e9477f --> -- [View Session](https://junior-prod.sentry.dev/conversations/agent%3A69da19b385017e68b7f9eace56e9477f) [[Sentry]](https://sentry.sentry.io/explore/conversations/agent%3A69da19b385017e68b7f9eace56e9477f/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes
.github/workflows/cascade-to-sentry-docs.yml.The cascade ran
gh workflow run "Bump API Schema SHA"in sentry-docs on every push tomain. getsentry/sentry-docs#20679 renamed that workflow to Bump @sentry/api, so dispatching it by the old name no longer works. sentry-docs now builds its API reference from@sentry/api/docsand bumps@sentry/apihourly on its own, so it doesn't need a dispatch from this repo.After this, nothing in this repo's workflows reads the
SENTRY_API_SCHEMA_UPDATER_APP_CLIENT_IDvariable or theSENTRY_API_SCHEMA_UPDATER_PRIVATE_KEYsecret. A repo admin can remove them unless something outside the workflows still needs them.via @BYK.
--
View Session [Sentry]