chore: update demo deploy cadence to be on tag (instead of main)#556
Merged
brendan-kellam merged 1 commit intomainfrom Oct 8, 2025
Merged
chore: update demo deploy cadence to be on tag (instead of main)#556brendan-kellam merged 1 commit intomainfrom
brendan-kellam merged 1 commit intomainfrom
Conversation
Contributor
|
@brendan-kellam your pull request is missing a changelog! |
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Updates the demo deploy cadence to be on tag instead of main. The reasoning is that I would like to make breaking REST API changes (like in #555) without having to spin a new release. However, MCP depends on the demo instance's REST api not breaking (on non-version changes), so that complicates things.
Whether we should worry about breaking public MCP is a separate discussion. For now, let's avoid breaking it.