Skip to content

ci(mcp-core): Regenerate create_project platform setup data daily - #2381

Merged
dcramer merged 1 commit into
mainfrom
ci/regenerate-platform-setup
Nov 18, 2026
Merged

dcramer merged 1 commit into
mainfrom
ci/regenerate-platform-setup

Conversation

@sentry-junior

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

Copy link
Copy Markdown
Contributor

create_project's platform setup data (platforms.json), added in #2358, is regenerated by hand today. This adds regenerate-platform-setup.yml, which runs daily and on manual dispatch from main. It runs pnpm --filter @sentry/mcp-core run generate-platform-setup and keeps one PR with any changes on the fixed bot/regenerate-platform-setup branch. scripts/platform-setup-pr.mjs decides what to do:

  • The generated data matches main, or matches the open PR: nothing. No commit, no push, no PR.
  • The data changed and no PR is open: commit it on a branch from main, force-push the bot branch (this overwrites a leftover branch from a closed PR), and open the PR.
  • The data changed and the open PR has older data: rebuild the branch from main and 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.yml rolling-PR pattern: the release bot (SENTRY_RELEASE_BOT_CLIENT_ID / SENTRY_RELEASE_BOT_PRIVATE_KEY, already used by release.yml and bump-sentry-api.yml) pushes and opens the PR so test.yml runs on it. Commits use the github-actions[bot] identity, like that bump. This assumes the release bot can push branches and open PRs in this repo, which bump-sentry-api.yml already relies on.

Running the generator locally against current sources left platforms.json unchanged.

via @dcramer.

--

View Session [Sentry]

@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sentry-local Ready Ready Preview Nov 18, 2026 5:16pm UTC

Request Review

Base automatically changed from feat/create-project-setup-knowledge to main November 18, 2026 17:15
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
dcramer force-pushed the ci/regenerate-platform-setup branch from 6c74554 to dfc9c5f Compare November 18, 2026 17:15
@dcramer
dcramer marked this pull request as ready for review November 18, 2026 17:15
@dcramer
dcramer requested a review from a team as a code owner November 18, 2026 17:15
@sentry-junior
sentry-junior Bot requested a review from dcramer November 18, 2026 17:15
@github-actions github-actions Bot added the risk: medium PR risk score: medium label Nov 18, 2026
@dcramer
dcramer merged commit b3ef665 into main Nov 18, 2026
42 checks passed
@dcramer
dcramer deleted the ci/regenerate-platform-setup branch November 18, 2026 17:26

This branch was successfully deployed

1 active deployment
Preview — dfc9c5f9 Deployed Nov 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium PR risk score: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant