chore(deps): update dependency react-select to v5 by renovate[bot] · Pull Request #111 · settlemint-archive/hyperledger-explorer

884f1c42 #5758 Thanks @Ke1sy! - 1. Added 'aria-activedescendant' for input and functionality to calculate it;
1. Added role 'option' and 'aria-selected' for option;
2. Added role 'listbox' for menu;
3. Added tests for 'aria-activedescendant';
4. Changes in aria-live region:
- the instructions how to use select will be announced only one time when user focuses the input for the first time.
- instructions for menu or selected value will be announced only once after focusing them.
- removed aria-live for focused option because currently with correct aria-attributes it will be announced by screenreader natively as well as the status of this option (active or disabled).
- separated ariaContext into ariaFocused, ariaResults, ariaGuidance to avoid announcing redundant information and higlight only current change.

`v5.7.7`

Compare Source

Patch Changes

224a8f0d #5666 Thanks @yhy-1! - Add aria-disabled to select's control component.

`v5.7.6`

Compare Source

Patch Changes

f6315cd5 #5672 Thanks @tu4mo! - Fix for calling non-cancellable scroll events

`v5.7.5`

Compare Source

Patch Changes

9d1730ba #5347 Thanks @aszmyd! - Make scroll lock div work on a document context it belongs to

`v5.7.4`

Compare Source

Patch Changes

16414bb5 #5689 Thanks @Rall3n! - Resolve defaultProps deprecation warning for React v18+.

`v5.7.3`

Compare Source

Patch Changes

59513d00 #5626 Thanks @emmatown! - Fix importing react-select in Node ESM

`v5.7.2`

Compare Source

Patch Changes

925cd4a2 #5536 Thanks @Rall3n! - required prop accessibiltiy and functionality improvements

`v5.7.1`

Compare Source

Patch Changes

597143ee #5559 Thanks @gdiazdelaserna! - Add exports field in package.json

`v5.7.0`

Compare Source

Minor Changes

0773095f #5457 Thanks @nderkim! - Add classNames API and unstyled prop

`v5.6.1`

Compare Source

Patch Changes

cda16826 #5482 Thanks @nderkim! - Fix unstable theme rerendering menu

`v5.6.0`

Compare Source

Minor Changes

c37e86d8 #4882 Thanks @Rall3n! - Add required prop

`v5.5.9`

Compare Source

Patch Changes

851ed2b8 #5430 Thanks @Rall3n! - Fix focused option if defaultMenuIsOpen is set

`v5.5.8`

Compare Source

Patch Changes

1ad6de4e #5084 Thanks @kosciolek! - When focusing a dropdown option, the numbers included in the aria live region take filtering into consideration.

`v5.5.7`

Compare Source

Patch Changes

0ca2d5ba #5431 Thanks @nderkim! - Change class components to functional components

`v5.5.6`

Compare Source

Patch Changes

92398939 #5409 Thanks @lukebennett88! - Move files around to as to be compatible with version 2 of @preconstruct/cli

`v5.5.5`

Compare Source

Patch Changes

0dd38029 #5246 Thanks @Rall3n! - Fix re-focus of component in Firefox if being disabled while focused

`v5.5.4`

Compare Source

Patch Changes

ebb0a17a #5404 Thanks @Methuselah96! - Use ResizeObserver to auto-update menu position if available

`v5.5.3`

Compare Source

Patch Changes

07656aaa #5399 Thanks @dependabot! - Update memoize-one

`v5.5.2`

Compare Source

Patch Changes

00238f1a #5376 Thanks @lukebennett88! - Fix bug with animated multi-value select width being too wide

`v5.5.1`

Compare Source

Patch Changes

0f6ef093 #5381 Thanks @Methuselah96! - Disable use of ResizeObserver for menu position auto-updating to avoid potential breaking changes.

`v5.5.0`

Compare Source

Minor Changes

598f9ee0 #5256 Thanks @Methuselah96! - Auto-update menu position when using menu portalling

`v5.4.0`

Compare Source

Minor Changes

5d49f70a #5249 Thanks @Methuselah96! - Export formatOptionLabel types (i.e., FormatOptionLabelMeta and FormatOptionLabelContext).

`v5.3.2`

Compare Source

Patch Changes

1f140e42 #5177 Thanks @Methuselah96! - Fix view height used for menu positioning to be the scroll parent instead of the window

`v5.3.1`

Compare Source

Patch Changes

03bf7351 #5164 Thanks @Methuselah96! - Bump @emotion/react to ^11.8.1 to avoid useInsertionEffect bug

`v5.3.0`

Compare Source

Minor Changes

c7d8d4b3 #5133 Thanks @nil4! - Update peerDependencies to include React 18

Patch Changes

0aaa9575 #5134 Thanks @rkulinski! - Use defaultPrevented to skip duplicate event handler for clicking select.
87e14431 #5131 Thanks @pcorpet! - Avoid referencing an ID that is not in the DOM
7184d538 #5082 Thanks @Methuselah96! - Fix type inference for Async's loadOptions prop
bd4ee8ae #5057 Thanks @Rall3n! - Prevent transition props from being forwarded to <input> element in DummyInput component

`v5.2.2`

Compare Source

Patch Changes

940a50b1 #4928 Thanks @Methuselah96! - Fix usage with esModuleInterop disabled
54f9538e #4941 Thanks @prichey! - Use React's AriaAttributes type directly rather than recreating
e97d45c0 #4908 Thanks @vjee! - Make 3rd argument of CommonProps['setValue'] optional.

`v5.2.1`

Compare Source

Patch Changes

f172d7f9 #4886 Thanks @Akridian! - Hooks for creation of custom Selects are now exported from main entry

`v5.2.0`

Compare Source

Minor Changes

6c7a3d1e #4785 Thanks @Rall3n! - Add prevInputValue to action meta
b522ac65 #4860 Thanks @ebonow! - Fix animated MultiValue transitions when being removed and change method used to generate unqiue keys for Option components. Closes #4844 , closes #4602

Patch Changes

417e7217 #4842 Thanks @Methuselah96! - Remove src directory from published package
480ea85b #4846 Thanks @Methuselah96! - Add missing index to MultiValue props type
b8e34472 #4854 Thanks @mikunpham! - Make input container css re-compute whenever input value changes due to a bug from @emotion/react in development env.

`v5.1.0`

Compare Source

Minor Changes

8b38d49b #4807 Thanks @hcharley! - Export AsyncCreatableProps from creatable entrypoint
46eeda1a #4801 Thanks @Methuselah96! - Export more types from main entry point

Patch Changes

fdd01e66 #4833 Thanks @ebonow! - Value container display property should be grid when isMulti and has no value so the Placeholder component is positioned correctly with the Input
0937604f #4823 Thanks @mikunpham! - Fix the issue where input contents are moved to the left due to multiple space characters.
ec80b577 #4803 Thanks @Methuselah96! - Import CSSObject from @emotion/react instead of @emotion/serialize

`v5.0.0`

Compare Source

Upgrade Guide

Summary

Convert to TypeScript (#4489) - TypeScript types now come packaged with react-select so you no longer need to have @types/react-select installed; we no longer include Flow types
Drop IE11 support (#4625, #4720, #4634) - this allows us to make changes to our CSS that we've wanted to make for a long time as well as remove unnecessary JS solutions (those changes are noted below)
Use forwardRef for all wrapped components (#4489) - this means that if you were accessing anything on the Select instance using a ref, the ref will now reference the internal Select directly (see below for how to upgrade)
Replace HOCs with hooks (#4489) - if you were using our HOCs to create custom Selects (i.e., makeCreatableSelect, mangeState, makeAsyncSelect) these have now been replaced by hooks (i.e., useCreatable, useStateManager, useAsync)
Remove dependency on AutosizeInput (#4625) - our new solution uses CSS grid which IE11 does not fully support; also .prefix__input now targets the input and NOT the container
Improve screen reader experience (#4676) - this isn't a breaking change in the API but it does change the screen reader announcements
Use CSS grid for single value layout (#4720) - this also isn't a breaking change in the API but is it a change in the styles since it switches to using CSS grid (not fully supported by IE11) for single-value Selects
Remove readonly attribute on our DummyInput (#4634) - this results in better accessibility but uses caret-color which is not available on IE11

Details

Convert to TypeScript

We've rewritten react-select in TypeScript which means you can remove any dependencies on @types/react-select. If you were using the Flow types than look into contributing types for v5 to flow-typed.

Here are the most notable changes when replacing @types/react-select with our packaged types:

@types/react-select	react-select	Notes
`OptinTypeBase`	no replacement	Options can be any type (if using `getOptionValue` and `getOptionLabel`) so there's no longer a base type for options
`OptionsType`	`Options`
`GroupTypeBase`	`GroupBase`
`GroupedOptionsType`	no replacement	This is equivalent to `ReadonlyArray<Group>`
`ValueType`	`OnChangeValue`
`InputActionTypes`	`InputAction`
`NamedProps`	`Props`
`Select` (the `ref` type)	`SelectInstance`	See "Use `forwardRef` for all wrapped components" for more details
`AsyncSelect` (the `ref` type)	`SelectInstance`	See "Use `forwardRef` for all wrapped components" for more details
`CreatableSelect` (the `ref` type)	`SelectInstance`	See "Use `forwardRef` for all wrapped components" for more details
`AsyncCreatableSelect` (the `ref` type)	`SelectInstance`	See "Use `forwardRef` for all wrapped components" for more details

If you were previously importing a type from the src directory when using @types/react-select:

import { ... } from 'react-select/src/...';

These should now be imported from the dist/declarations/src directory:

import { ... } from 'react-select/dist/declarations/src/...';

We export any types from the main entry point that we think might be useful to the user. If you are using a type that is not exported from the main entry point please open a PR or issue so that we can add it.

If you are using custom props for the Select component you can use module augmentation to add them to the Select prop types:

declare module 'react-select/dist/declarations/src/Select' {
  export interface Props<
    Option,
    IsMulti extends boolean,
    Group extends GroupBase<Option>
  > {
    myCustomProp: string;
  }
}

Drop IE11 support

This allows us to use modern CSS in order to improve the quality of react-select and remove excessive JavaScript code to work around not having the ability to use modern CSS. If you need IE11 support either:

Stay on v4.
Attempt to use our Styles API and/or Components API to override styles and/or components that don't support IE11. The only change that might be hard to override is "Remove readonly attribute on our DummyInput" since you can't override the DummyInput component with the Styles or Components API.
If there are simple changes that make react-select compatible with IE11, open a PR. We are unlikely to provide official support for IE11 since supporting IE11 makes maintaining react-select a lot more difficult and holds us back from changes we want to make, but we also are glad to accept simple changes if they make your life easier.

Use `forwardRef` for all wrapped components

NOTE: Accessing any of the internals of the Select component using refs is not part of our public API. The internals of the Select component can change at any time (including in minor and patch releases). The only methods on the Select component that are part of the public API are the focus() and blur() methods.

react-select exports five components: BaseSelect, CreatableSelect, Select (the default export), AsyncSelect, AsyncCreatableSelect. The last four components are wrappers around the BaseSelect. Previously the ref for each of these components was pointing to itself, but now we use forwardRef which means that the refs for all five components now point to BaseSelect.

The focus() and blur() methods are untouched by this change. However if you were accessing the internals of the BaseSelect component, you will need to update how you were accessing the BaseSelect. Here is how to update access to the BaseSelect component:

Component	v4	v5
`BaseSelect`	`ref`	`ref`
`CreatableSelect`	`ref.select.select`	`ref`
`Select`	`ref.select`	`ref`
`AsyncSelect`	`ref.select.select`	`ref`
`AsyncCreatableSelect`	`ref.select.select.select`	`ref`

Replace HOCs with hooks

The primary reason for this change is that hooks combined with generic components are easier to type in TypeScript than HOCs combined with generic components. These HOCs/hooks are considered advanced usage.

If you were using the HOCs, it shouldn't be too hard to replace them with its corresponding hook (i.e., useStateManager, useCreatable, or useAsync). As an example, here is how the state managed Select (the default export) used to be constructed with the mangeState HOC:

const Select = manageState(SelectBase);

With hooks it is now constructed like this:

const Select = (props) => {
  const baseSelectProps = useStateManager(props);
  return <SelectBase {...baseSelectProps} />;
}

Consult the source code for how the other components are constructed.

Remove dependency on AutosizeInput

This is an exciting change because we get to drop our dependency on react-input-autosize. We now use a pure CSS solution to auto-size the input, however this means that we have to drop support for IE11 since IE11 does not fully support CSS grid. As part of this refactor the .prefix__input CSS class now targets the input itself and NOT the container. See #4625 for more details.

Improve screen reader experience

The following improvements have been made for screen reader users:

NVDA now announces the context text when initially focused
Selected option(s) (single and multi) are now announced when initially focused
VoiceOver now announces the context text when re-focusing
The clear action is now announced
Placeholder text is now announced
Mobile VoiceOver is now able to remove selected multi options

Also we've added the role of combobox and the required ARIA attributes to the Input and DummyInput components to allow JAWS support and a better screen reader experience overall. See #4695 for more details.

Use CSS grid for single value layout

Previously the absolution positioning of both the value and the placeholder pulled them out of the flow, and thus the component itself collapsed down when used as a flex child. To solve this we are now using CSS grid for the single value layout.

Remove `readonly` attribute on our `DummyInput`

Previously we added the readonly attribute to the DummyInput (when isSearchable is set to false) in order to hide the flashing cursor and prevent devices from showing a virtual keyboard. However the readonly attribute causes the DummyInput to be removed from the tab order in iOS Safari. In order to solve this we're replacing the readonly attribute with setting the caret-color CSS prop (which IE11 does not support) to transparent and setting the inputMode attribute on the <input> to none.

Changelog

Major Changes

ef87c3ac #4683 Thanks @Methuselah96! - React-Select has been converted from Flow to TypeScript.

Other changes for v5 include usage of forwardRef, new hooks for stateManager, async and creatable components, and more reliable filtering implementaion with new options in the creatable variant.

Patch Changes

10225290 #4720 - Updated the layout for the singleValue input/placeholder/container so that it works better when used in flex layouts.
53f1972b #4731 Thanks @JedWatson! - MultiValue key now includes a hyphen between the value and the index to prevent edge cases where you could get a duplicate key error
b41f4ceb #4704 Thanks @Rall3n! - Fix findDOMNode deprecation by adding refs to transition components
4b028829 #4634 - The readonly attribute has been removed from the DummyInput to improve accessibility
7fcec537 #4697 - Add the role of combobox and the required ARIA attributes to the Input and DummyInput components to allow JAWS support and a better screen reader experience overall.
ca2c0e5b #4756 Thanks @fdcds! - Add option field to type of CreateOptionActionMeta
9e82aadc #4676 - The following improvements have been made for screen reader users:
- NVDA now announces the context text when initially focused
- Selected option/s (single and multi) are now announced when initially focused
- VoiceOver now announces the context text when re-focusing
- The clear action is now announced
- Placeholder text is now announced
- Mobile VoiceOver is now able to remove selected multi options
638f5455 #4702 Thanks @Methuselah96! - The Option generic is no longer required to extend the OptionBase type
23cea0b5 #4782 Thanks @Methuselah96! - Fix type of loadingMessage prop to allow it to return any ReactNode

`v4.3.1`

Compare Source

Patch Changes

2c915d10 #4577 - Bump @emotion/cache to v11.4.0 which fixes an issue where different versions of Emotion running at the same time causes styles to disappear in production.

`v4.3.0`

Compare Source

Minor Changes

035294f4 #3360 Thanks @sunniejai!
- focusedOption is now passed to the MenuList Component as a prop

Patch Changes

7a414a7c #3262 Thanks @torkelo!
- The Menu bottom is no longer scrolled into view when menuShouldScrollIntoView=false

Documentation Updates

#4109 Thanks @manvydasu
- Replaced componentWillReceiveProps with componentDidUpdate in docs

`v4.2.1`

Compare Source

Patch Changes

ca3c41bb #4478 Thanks @ebonow! - Check passive events polyfill for the existence of window for SSR

`v4.2.0`

Compare Source

Minor Changes

2ffed9c6 #4444 Thanks @Rall3n! - Use accessor props to get value and label in compareOption
2baf5a9d #4414 Thanks @ebonow! - Add ariaLiveMessages prop for internationalization and other customizations, add aria-live prop, and other accessibility fixes. Inspired heavily from the work done by @Kashkovsky, @radegran, @Malgalad, and @TheHollidayInn - thanks to them, @bozdoz for the thorough testing and recommendations, and for everyone who contributed constructive feedback towards a better accessibility experience.
7cdb8a6b #4391 Thanks @ebonow! - Pass and sanitize CommonProps passed to Group and Input components

Patch Changes

c955415c #4437 Thanks @ebonow! - Set event listeners to be non-passive to remove Chrome console warnings
3ca22b2f #3827 Thanks @mitchellhamilton! - Memoize stripDiacritics in createFilter for the input with memoize-one so that stripDiacritics is not called for the same string as many times as there are options every time the input changes

Inspired by https://blog.johnnyreilly.com/2019/04/react-select-with-less-typing-lag.html
dce3863f #4423 Thanks @Methuselah96! - Remove browser alias fields in order to fix SSR apps
ec7c0728 #4443 Thanks @ebonow! - Allow tabIndex prop Type to be number or string

`v4.1.0`

Compare Source

Minor Changes

b5f9b0c5 #4342 Thanks @Methuselah96! - Standardized innerProps and className props on customizable components
19b76342 #3911 Thanks @eugenet8k! - Add removedValues to onChange event meta when the action is clear (when the user clears the value in the Select)

Patch Changes

f600d13f #4422 Thanks @Methuselah96! - Fix finding focusable options for groups
a016c878 #4420 Thanks @Methuselah96! - Bump dependency on @babel/runtime in order to fix compatibility issues with Webpack 5
10b5f5a5 #4404 Thanks @Methuselah96! - Remove unnecessary dependency on @emotion/css

`v4.0.2`

Compare Source

Patch Changes

44f285b0 #4399 Thanks @Methuselah96! - Fixed building focusable options from groups

`v4.0.1`

Compare Source

Patch Changes

645feb3e #4396 Thanks @Methuselah96! - Fixed keys for options within groups

`v4.0.0`

Compare Source

Upgrade Guide

Summary

Standardize value passed to onChange (https://github.com/JedWatson/react-select/pull/4339) - the onChange handler is now always passed an array of options if isMulti is set to true
Emotion 11 (https://github.com/JedWatson/react-select/pull/4283) - should only affect you if you're using the NonceProvider component
Remove usage of UNSAFE React methods (https://github.com/JedWatson/react-select/pull/4313) - shouldn't affect you except now you won't see those warning messages in the console anymore

Details

Standardize value passed to `onChange`

This change makes it so that the first parameter passed to the onChange callback will now always be an array of options if isMulti is set to true and will always be a single option or null if isMulti is set to false. Previously the first parameter of onChange could be an array or null when isMulti was set to true.

That means if you were previously using nullish coalescing in order to handle null for isMulti:

<Select
  isMulti
  onChange={(newValues) =>  setValues(newValues ?? [])}
/>

You can now remove the nullish coalescing because onChange will always be an array when isMulti is set to true:

<Select
  isMulti
  onChange={(newValues) =>  setValues(newValues)}
/>

Emotion 11

The NonceProvider component now requires a cacheKey prop that corresponds to the newly required key prop for the Emotion cache. This won't affect you if you aren't using NonceProvider. See #4283 for more details.

Remove usage of UNSAFE React methods

This isn't necessarily a breaking change, but it required a large refactor in order to accomplish so we released this in a major upgrade in case it has some unintended consequences.

Changelog

Major Changes

02050675 #4339 Thanks @Methuselah96! - Standardized value passed to onChange
26b6325c #4283 Thanks @majgaard! - Upgrades Emotion dependency to v11.0.0

BREAKING CHANGE: The NonceProvider component now requires a cacheKey prop that corresponds to the key for the Emotion cache.
b2488bb5 #4313 Thanks @Methuselah96! - Removed usages of UNSAFE React methods

Patch Changes

2d5496d5 #4388 Thanks @Methuselah96! - Removed memoization of buildMenuOptions

`v3.2.0`

Compare Source

Minor Changes

c615e93d #4084 Thanks @JedWatson! - Changed the cx and getValue props that are passed to components into instance properties, which means they now pass a referential equality check on subsequent renders.

This is helpful, for example, when you're optimising the performance of rendering custom Option components - see #3055
72f6036f #4306 Thanks @bladey! - Remove duplicate prop createOptionPosition

Patch Changes

ee638d46 #4275 Thanks @Methuselah96! - Adds react ^17.0.0 to peer dependencies for React 17 support
a0133f19 #4154 Thanks @brenshanny! - Creatable: Fixed removing MultiValues that have identical values. See issue #4137 for details.
d1e660c6 #4213 Thanks @eythort! - Added a guard to the ScrollCaptor component to check that el exists before calling removeEventListener, fixes intermittent errors
a1e1db25 #4373 Thanks @Methuselah96! - Fixed value passed to onChange when clearing value
2ad29d61 #4136 Thanks @Methuselah96! - Base aria-live message on tabSelectsValue prop
ad890f27 #4326 Thanks @Methuselah96! - Updated react-input-autosize to v3.0.0
b28d9922 #3990 Thanks @nikitaindik! - Fixed onCreateOption is not always called for Creatable
24ba8702 #4289 Thanks @slimklim! - Added innerProps prop to the built-in MenuList component to reduce the need for additional DOM nodes or forking internal code when passing additional props to the DOM element the MenuList component is rendering.

See issue #4265 for an explanation.

`v3.1.1`

Compare Source

Patch Changes

c8d74bd5 #3979 Thanks @mitchellhamilton! - Fix repository field
c8447f48 #4034 Thanks @sophiebits! - Improve performance of option filtering when ignoreAccents is enabled (the default)
7af1aafb #4295 Thanks @JedWatson! - Fix menuplacement context
32ad5c04 #3892 Thanks @flexdinesh! - Fix react-select ignoring HTML5 "form" attribute
6af14fbb #3897 Thanks @lorisdev! - Removes the call to onMenuOpen on every input change

If you were relying on this undesired behavior it may be a breaking change.
Please upgrade accordingly.
0eb1ef96 Thanks @JedWatson! - Fixes touch issues in IE11
ad608c8f #3928 Thanks @dpordomingo! - Update MenuPlacer context usage in order to the new React Context API

`v3.1.0`

Compare Source

Minor Changes

4cf6c43c #3690 Thanks @JedWatson! - Add isLoading prop support to the AsyncSelect component (see #3690)

Patch Changes

83b48de4 [#3868](https://redir

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

sourcery-ai · 2025-01-24T13:20:55Z

Reviewer's Guide by Sourcery

This pull request updates the react-select dependency from version 1.2.1 to 5.0.0. This is a major version update, which includes breaking changes and new features.

Class diagram showing key changes in react-select v5

classDiagram
    class Select {
      +onChange(value)
      +focus()
      +blur()
    }
    class SelectInstance {
      +focus()
      +blur()
    }
    class Props {
      +isMulti: boolean
      +required: boolean
      +classNames: object
      +unstyled: boolean
      +ariaLiveMessages: object
    }
    Select -- Props
    Select -- SelectInstance : forwards ref to

File-Level Changes

Change	Details	Files
Updated react-select dependency to v5	Updated react-select dependency from ^1.2.1 to ^5.0.0 in package.json. Updated react-select dependency in package-lock.json.	`client/package.json` `client/package-lock.json`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!
Generate a plan of action for an issue: Comment @sourcery-ai plan on
an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

sourcery-ai

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

sourcery-ai Bot reviewed Jan 24, 2025

View reviewed changes

chore(deps): update dependency react-select to v5

e5e41da

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate Bot force-pushed the renovate/react-select-5.x branch from 36e0f28 to e5e41da Compare January 24, 2025 13:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency react-select to v5#111

chore(deps): update dependency react-select to v5#111
renovate[bot] wants to merge 1 commit intomainfrom
renovate/react-select-5.x

renovate Bot commented Jan 24, 2025 •

edited

Loading

Uh oh!

sourcery-ai Bot commented Jan 24, 2025 •

edited

Loading

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai Bot left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Jan 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Upgrade Guide

Summary

Details

Convert to TypeScript

Drop IE11 support

Use forwardRef for all wrapped components

Replace HOCs with hooks

Remove dependency on AutosizeInput

Improve screen reader experience

Use CSS grid for single value layout

Remove readonly attribute on our DummyInput

Changelog

Major Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Documentation Updates

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Upgrade Guide

Summary

Details

Standardize value passed to onChange

Emotion 11

Remove usage of UNSAFE React methods

Changelog

Major Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

renovate Bot commented Jan 24, 2025 •

edited

Loading

Use `forwardRef` for all wrapped components

Remove `readonly` attribute on our `DummyInput`

Standardize value passed to `onChange`

sourcery-ai Bot commented Jan 24, 2025 •

edited

Loading