Skip to content

ci(api): Dispatch the toolkit @sentry/api bump on each api@ release - #131244

Merged
BYK merged 3 commits into
masterfrom
ci/api-dispatch-toolkit-bump
Nov 16, 2026
Merged

BYK merged 3 commits into
masterfrom
ci/api-dispatch-toolkit-bump

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

getsentry/toolkit#2291 added toolkit's bump-sentry-api.yml, which keeps one PR on the newest @sentry/api release so toolkit's CI checks the CLI and MCP packages against it (part of #131204). It runs on a daily schedule. This change also dispatches it from bump-sentry-docs.yml whenever an api@ release is published, next to the existing sentry-docs dispatch, so toolkit picks up each release as it ships.

  • The dispatches are one matrix job with an entry for sentry-docs and one for toolkit. Each entry names the repo, the workflow file, the ref, and the app that can dispatch there. The entries run in parallel without fail-fast, so one failing doesn't cancel the other, and adding a downstream repo is one more entry.
  • sentry-docs keeps its existing app. The toolkit entry uses the release bot app (SENTRY_RELEASE_BOT_*), which this repo's bump-sentry-in-getsentry.yml and toolkit's own workflows already use, scoped to getsentry/toolkit with actions: write.
  • Both dispatches wait for a wait-for-npm job. It polls npm until it serves the release's version, for up to about 10 minutes. Craft publishes to npm before the GitHub release, but the registry can lag, and a bump dispatched too early would still read the previous version.
  • ci: Keep one rolling PR on the newest @sentry/api release toolkit#2291 has merged, so bump-sentry-api.yml now exists on toolkit's main.
  • Toolkit's daily schedule stays as a fallback.
  • Open question: does the release bot's installation have actions: write on toolkit? If it doesn't, the toolkit dispatch fails and the daily schedule still picks the release up.

via @BYK.

--

View Session [Sentry]

getsentry/toolkit keeps one PR on the newest @sentry/api release so its CI
checks the CLI and MCP packages against it. Dispatching that workflow from
the release here runs it as the release ships, instead of waiting for its
daily schedule. The token comes from the release bot app, which this repo
and toolkit both already use.
The npm registry can take a few minutes to serve a version craft just
published, so a dispatched bump could still read the previous one. A
wait-for-npm job now polls npm for the release's version, and the
sentry-docs and toolkit dispatches run after it.
@sentry-junior
sentry-junior Bot requested a review from a team as a code owner November 16, 2026 14:04
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 16, 2026
Comment thread .github/workflows/bump-sentry-docs.yml Resolved
The sentry-docs and toolkit dispatches were two copies of the same job.
A matrix runs them in parallel, without fail-fast, and adding or removing
a downstream repo is now one entry.
@sentry-junior
sentry-junior Bot requested a review from BYK November 16, 2026 16:20
Comment thread .github/workflows/bump-sentry-docs.yml Resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant