Repository navigation
Conversation
dacdao1
marked this pull request as ready for review
October 15, 2026 19:08
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.
Redis-free editor collaboration needs a single serving process during upgrades. This sets
Recreatefor Redis-free singleton deployments in both combined and split-server modes, exposes the effective maximum editor replica count (including HPA), and requires shared Redis for Redis-configured rolling deployments. Scheduler replicas remain independent.Companion to https://github.com/mage-ai/mage-pro/pull/2327, addressing Johnson's single-server compatibility and upgrade-overlap request. Preserves legacy
envprecedence and prevents caller env entries from understating the generated topology/Redis requirement. Chart version: 0.2.17.Release order
Publish this chart and refresh the cached
mageaiHelm repository metadata in upgrading Cloud backends, then apply the chart before or with the new Mage Pro app image. Publishing the chart alone does not refresh running backends' cached indexes. Verify the selected chart version and rendered strategy/env before rollout.Validation