Update dependency chakra-react-select to v6 (master) - #1653
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/master-chakra-react-select-6.x
branch
from
July 25, 2026 01:18
bef2b34 to
84465d3
Compare
renovate
Bot
force-pushed
the
renovate/master-chakra-react-select-6.x
branch
3 times, most recently
from
August 8, 2026 01:02
ac5e869 to
dbcdd27
Compare
renovate
Bot
force-pushed
the
renovate/master-chakra-react-select-6.x
branch
from
August 16, 2026 10:46
dbcdd27 to
32e4be1
Compare
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.
This PR contains the following updates:
4.10.1→6.1.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
csandman/chakra-react-select (chakra-react-select)
v6.1.3: 6.1.3Compare Source
What's Changed
Full Changelog: csandman/chakra-react-select@v6.1.1...v6.1.3
v6.1.1: 6.1.1Compare Source
What's Changed
Full Changelog: csandman/chakra-react-select@v6.1.0...v6.1.1
This was released November 14, 2025, I just forgot to create the actual release 😅
v6.1.0: 6.1.0Compare Source
What's Changed
selectedOptionColorPalettevalues pulled from the theme by @csandman in #364colorPalette.300andcolorPalette.500for the selected option background colors, the semantic tokencolorPalette.solidwill be used instead. And for the option label, the text color will becolorPalette.contrast.ColorPalettetype by @saalto-it in #362New Contributors
Full Changelog: csandman/chakra-react-select@v6.0.1...v6.1.0
v6.0.1: 6.0.1Compare Source
What's Changed
Full Changelog: csandman/chakra-react-select@v6.0.0...v6.0.1
v6.0.0: 6.0.0Compare Source
Finally, a Chakra V3 compatible version of Chakra React Select is ready to go! There were many breaking changes in the V3 release of Chakra UI, so this version took a while, but it's now ready for use in production. Thanks to everyone who tested out the pre-releases and gave feedback.
The docs should be fully updated, but if anything doesn't make sense after the release, don't hesitate to post an issue or a discussion. Unfortunately, due to the size of this release, there won't be a codemod available for migrating (similar to the core Chakra library). Here are all of the breaking changes that should be noted when upgrading.
Breaking Changes
Selectcomponent.Control, which still uses styles from theInputtheme, and theMultiValuecomponents, which still pull their styles from theTagtheme. The docs have been updated to list out which theme styles are being used for each React Select sub-component: https://github.com/csandman/chakra-react-select#theme-styles.colorSchemeis now namedcolorPalette: https://www.chakra-ui.com/docs/get-started/migration#colorscheme-proptagColorSchemeis nowtagColorPalette.selectedOptionColorSchemeis nowselectedOptionColorPalette.colorSchemekey is nowcolorPalette.chakraComponents.LoadingIndicator:emptyColoris nowtrackColor(this isn't a real prop, but it maps to the--spinner-track-colorcss variable).speedis nowanimationDuration.thicknessis nowborderWidth.colorPalettewas also added to the loading indicator which can be used to set the color without specifying a token number (responds better to changes between light and dark mode).LoadingIndicatorcomponent no longer changes size in response to changes to the rootsizeprop. With the new default size, the default spinner size ended up looking the best across all three select sizes.focusBorderColorwas replaced withfocusRingColoranderrorBorderColorwas removed, as there is no longer any equivalent prop that exists.isprefix removed: https://www.chakra-ui.com/docs/get-started/migration#boolean-propsisRequiredis now therequiredattribute that's already built-in toreact-select. It will behave the same as therequiredprop on any other Chakra component.isReadOnlyis nowreadOnlyisInvalidis nowinvalid. This prop was removed from the coreInput,Select, andTextareacomponents in the Chakra UI library in favor of passing them into a wrappingField.Root. However, they were left on this package due to many users not always wrapping theSelect: https://www.chakra-ui.com/docs/get-started/migration#input-select-textareadisabled, which will override theisDisabledprop built-in toreact-selectisDisabledprop from React Select will still function as it did previously.menuPlacementof"auto". This is to more closely match the default flipping behavior of the ChakraSelect.One other change to note is that most of the other custom StackBlitz demos were removed from the readme. These were very time consuming to maintain, so they were removed to prevent confusion. However, most of the advanced examples were added to the main demo, so if you'd like to see how any of them have changed, you can check there.
The main demo is now a direct copy of the demo project included in this repo. This should make maintenance much easier going forward, as this will always be the basis for testing future changes.
Full Changelog: csandman/chakra-react-select@v5.0.2...v6.0.0
v5.1.1: 5.1.1Compare Source
What's Changed
Full Changelog: csandman/chakra-react-select@v5.1.0...v5.1.1
v5.1.0: 5.1.0Compare Source
What's Changed
"auto"by @csandman in #373This change is to match the default flipping behavior of all Chakra UI popovers out of the box, and to align with the behavior in v6. This could be seen as a "breaking" change to some if you were reliant on the old behavior, so if you want to go back to the old behavior of having the select menu always stay below the input, pass the prop
menuPlacement="bottom"to your select.Full Changelog: csandman/chakra-react-select@v5.0.5...v5.1.0
v5.0.5: 5.0.5Compare Source
What's Changed
@deprecateddoc tag from thestyleprop by @csandman in #368Full Changelog: csandman/chakra-react-select@v5.0.4...v5.0.5
v5.0.4: 5.0.4Compare Source
What's Changed
--legacy-peer-depsanymore.Full Changelog: csandman/chakra-react-select@v5.0.3...v5.0.4
v5.0.3: 5.0.3Compare Source
What's Changed
New Contributors
Full Changelog: csandman/chakra-react-select@v5.0.2...v5.0.3
v5.0.2: 5.0.2Compare Source
What's Changed
Mostly some documentation/CI changes, along with a new build config.
exportsand modify the tsup build config by @csandman in #346importandrequire.Full Changelog: csandman/chakra-react-select@v5.0.1...v5.0.2
v5.0.1: 5.0.1Compare Source
What's Changed
isFixedattribute on options to remove the tag close button. This was supposed to be removed with the other breaking changes, but it was missed.react-selectdocs for how you can use custom components. Because of this, this should be done by the end user if desired.Full Changelog: csandman/chakra-react-select@v5.0.0...v5.0.1
v5.0.0: 5.0.0Compare Source
What's Changed
This is the last major release before Chakra v3 is fully released! The intention of this release is to batch a few breaking changes that have been in the works for a while, along with a codemod to hopefully make the changes for you.
Breaking Changes
useBasicStylesprop was removed, as the styles provided by it are now the default. Originally, it was styled to match theInputRightAddoncomponent, in order to create a visual separation between the dropdown indicator and the clear indicator. However, it seems that most people preferred it to visually match the original ChakraSelectcomponent, so those styles are now the default. If you want to modify the styles to appear like they used to, you can do so using thechakraStylesprop. Some examples of how to do this are provided in the README.selectedOptionColorprop. A new prop was added a while ago to replace that one,selectedOptionColorScheme, as some people were getting confused by the meaning of the original (thinking it meant an explicit color instead of a named color from their theme). The old one was left in the code though, and now it is gone for good.hasStickyGroupHeadersprop. This was removed from the documentation since v4.6.0, as it was only ever really an experimental way to style the grouped option headers so they'd stay in view while you scroll the list of options. It also had some problems with using the keyboard to navigate between options. They would disappear behind the header when you used the up arrow. There is an example for how these styles can be implemented usingchakraStylesin #343.colorSchemeprop totagColorScheme. There has been some confusion around what this prop actually means, as the original name the prop had wasn't specific enough to it's purpose. It didn't make sense to have a specific prop forselectedOptionColorScheme, and not be specific with the naming for thetagColorScheme. This may be followed by the addition of a new rootcolorSchemeprop, but that isn't included here.All of these changes can be made automatically using the Codemod provided here
This release will most likely mean an end of support for
v3(Chakra v1 compatible version), unless people want to put up any fix PRs for it themselves.Full Changelog: csandman/chakra-react-select@v4.10.1...v5.0.0
Configuration
📅 Schedule: (UTC)
* * * * 0,6)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.