Fake high version of RTC to support staged roll-out transition#100
Merged
maxschmeling merged 1 commit intotrunkfrom Jan 27, 2026
Merged
Conversation
chriszarate
approved these changes
Jan 27, 2026
maxschmeling
deleted the
fake-high-version-for-staged-rollout-transition
branch
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
2 participants
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.
We're transitioning the RTC integration to a staged roll-out. However, if we push a newer version to this repository, production will immediately pick it up once deployed and start using it because it finds and loads the latest version. This change allows us to pick up the existing version as the latest version until the
vip-go-mu-pluginschanges make their way into production to allow for specific version loading.Once those changes are in production, this can be reverted.