Skip to content

Releases: csandman/chakra-react-select

4.0.0-rc.2

13 May 18:37
Compare
Choose a tag to compare
4.0.0-rc.2 Pre-release
Pre-release

What's Changed

  • Fix the types being built by removing "increcemental" from tsconfig by @csandman in #124
    • In 4.0.0-rc.1 the types were not being published with the package, now they are.

Full Changelog: v4.0.0-rc.1...v4.0.0-rc.2

3.3.6

13 May 18:35
Compare
Choose a tag to compare

What's Changed

  • Fix the types being built by @csandman in #125
    • From 3.3.4 to 3.3.5 the types were not being published with the package, now they are.

Full Changelog: v3.3.5...v3.3.6

3.3.5

13 May 00:23
Compare
Choose a tag to compare

What's Changed

  • Move all Chakra UI packages from peerDependencies to dependencies in 78461eb
    • This is to fix a conflicting peer dependency issue that arose since the release of Chakra UI v2. It also mirrors the change already made in v4.0.0-rc.1.
    • This will hopefully prevent any issues from arising with peer dependencies not being installed as mentioned in #78
    • This is also how these "peer" dependencies are handled in each of the Chakra UI packages
    • As long as you are on a compatible version of @chakra-ui/react, each of these dependencies will be de-duplicated during install

Full Changelog: v3.3.4...v3.3.5

4.0.0-rc.1

12 May 21:14
Compare
Choose a tag to compare
4.0.0-rc.1 Pre-release
Pre-release

What's Changed

This is a test release for @chakra-ui/react@2. If it is stable it will be published as a full release. If you want to test it, you will need to update to @chakra-ui/react@2 and react@18 + react-dom@18 and follow Chakra's migration guide. When a full release is published the docs will be updated accordingly. A branch for chakra-react-select@3 will be maintained for the time being with any maintenance required for pre-chakra v2 being published to chakra-react-select@3.x.

  • Chakra UI v2 by @csandman in #120
    • Update all packages to Chakra UI v2 versions
    • Move all chakra packages to dependencies from peerDependencies
      • This will hopefully prevent any issues from arising with peer dependencies not being installed like mentioned in #78
      • This is also how these peer dependencies are handled in each of the Chakra UI packages
      • As long as the user is on a compatible version of @chakra-ui/react, each of these dependencies will be de-duplicated during install

Full Changelog: v3.3.4...v4.0.0-rc.1

3.3.4

12 May 20:40
Compare
Choose a tag to compare

What's Changed

Behind the Scenes

  • Update babel.config.js to closer match Chakra UI's
  • Update tsconfig.json to closer match Chakra UI's
  • Clean up package.json
    • Add a new format script
    • Add new tags
    • Downgrade react dev dependencies to match this version of chakra
    • Update remaining dev dependencies

Full Changelog: v3.3.3...v3.3.4

3.3.3

06 May 20:24
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.3.2...v3.3.3

3.3.2

06 May 16:12
Compare
Choose a tag to compare

What's Changed

  • Package Update by @csandman in #113
    • Add a prepublishOnly script to build before deploying
    • Update react-select to v5.3.1
    • Update all dev dependencies

Full Changelog: v3.3.1...v3.3.2

3.3.1

20 Apr 19:24
Compare
Choose a tag to compare

What's Changed

  • ChakraStylesConfig generic default fix by @csandman in #89
    • Change the default value for the IsMulti generic on the ChakraStylesConfig interface to be boolean instead of false
      • This is to fix any type errors from using the isMulti prop along with a ChakraStylesConfig object
      • This was made in response to #88

Full Changelog: v3.3.0...v3.3.1

3.3.0

18 Apr 20:58
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.2.0...v3.3.0

3.2.0

14 Apr 19:46
Compare
Choose a tag to compare

What's Changed

  • [ImgBot] Optimize images by @imgbot in #76
  • New react-select version + Minor tweaks by @csandman in #84
    • Update react-select to 5.3.0
    • Update all dev dependencies
    • The isReadOnly and isRequired props will not be forwarded from a wrapping form control to the <input> component
      • Only aria-required is added to the input, as it will not actually be filled when submitting a form so it should not block the submission when it is blank
    • Add the class-name-prefix--has-value class to the SelectContainer component when there is a value selected

Full Changelog: v3.1.2...v3.2.0