[scheduler] Update feedback banner to say beta instead of alpha#22804
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
rita-codes
added
docs
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
mbrookes
pushed a commit
to mbrookes/mui-x
that referenced
this pull request
Jun 27, 2026
…22804) Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
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.
Summary
The Scheduler has moved from alpha to beta, but the docs feedback banner still says "The Scheduler is in alpha". This updates the banner copy to reflect the current beta status.
Changes
docs/src/modules/components/overview/scheduler/SchedulerFeedbackBanner.tsx"🚀 The Scheduler is in alpha — we'd love your input." → "🚀 The Scheduler is in beta — we'd love your input."
I have followed (at least) the PR section of the contributing guide.