Repository navigation
ci(api): Dispatch the toolkit @sentry/api bump on each api@ release - #131244
Merged
Merged
Conversation
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.
BYK
requested changes
Nov 16, 2026
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.
BYK
approved these changes
Nov 16, 2026
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.
getsentry/toolkit#2291 added toolkit's
bump-sentry-api.yml, which keeps one PR on the newest@sentry/apirelease 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 frombump-sentry-docs.ymlwhenever anapi@release is published, next to the existing sentry-docs dispatch, so toolkit picks up each release as it ships.SENTRY_RELEASE_BOT_*), which this repo'sbump-sentry-in-getsentry.ymland toolkit's own workflows already use, scoped to getsentry/toolkit withactions: write.wait-for-npmjob. 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.bump-sentry-api.ymlnow exists on toolkit'smain.actions: writeon toolkit? If it doesn't, the toolkit dispatch fails and the daily schedule still picks the release up.via @BYK.
--
View Session [Sentry]