Repository navigation
chore: open MCP version bump PRs automatically - #490
Draft
mattrossman wants to merge 1 commit into
Draft
mattrossman wants to merge 1 commit into
mattrossman wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This was referenced Nov 6, 2026
This branch has not been 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.
Replaces the manual MCP version update in evals with a workflow that prepares a dependency bump PR when a new version is dispatched. The eval runtime now uses the exact platform-lite dependency version, so the two cannot drift.
The MCP release dispatch will trigger this workflow automatically: supabase/mcp#536. Once this workflow is on the default branch and Supabase Releaser has access to evals, verify the dispatch with a test run.
Ref AI-1389