Repository navigation
ci(mcp-core): Regenerate create_project platform setup data daily - #2381
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Add a scheduled workflow that reruns generate-platform-setup and keeps one PR with any changes on the bot/regenerate-platform-setup branch. It does nothing when the data matches main or the open PR, opens a PR when none is open, and force-pushes the branch to update an open one. Co-Authored-By: David Cramer <23610+dcramer@users.noreply.github.com>
dcramer
force-pushed
the
ci/regenerate-platform-setup
branch
from
November 18, 2026 17:15
6c74554 to
dfc9c5f
Compare
dcramer
marked this pull request as ready for review
November 18, 2026 17:15
dcramer
approved these changes
Nov 18, 2026
7 tasks done
This branch was successfully deployed
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.
create_project's platform setup data (platforms.json), added in #2358, is regenerated by hand today. This addsregenerate-platform-setup.yml, which runs daily and on manual dispatch frommain. It runspnpm --filter @sentry/mcp-core run generate-platform-setupand keeps one PR with any changes on the fixedbot/regenerate-platform-setupbranch.scripts/platform-setup-pr.mjsdecides what to do:main, or matches the open PR: nothing. No commit, no push, no PR.main, force-push the bot branch (this overwrites a leftover branch from a closed PR), and open the PR.mainand force-push it with a lease. The existing PR picks it up, and no second PR is opened.The PR is never merged automatically. It follows the
bump-sentry-api.ymlrolling-PR pattern: the release bot (SENTRY_RELEASE_BOT_CLIENT_ID/SENTRY_RELEASE_BOT_PRIVATE_KEY, already used byrelease.ymlandbump-sentry-api.yml) pushes and opens the PR sotest.ymlruns on it. Commits use thegithub-actions[bot]identity, like that bump. This assumes the release bot can push branches and open PRs in this repo, whichbump-sentry-api.ymlalready relies on.Running the generator locally against current sources left
platforms.jsonunchanged.via @dcramer.
--
View Session [Sentry]