Skip to content

Latest commit

 

History

History
776 lines (563 loc) · 31.1 KB

v1.8.5.mdx

File metadata and controls

776 lines (563 loc) · 31.1 KB
title description releaseUrl releaseDate version
Version 1.8.5
Explore the changelog for Chakra UI version 1.8.5. Learn about the latest features, bug fixes, and improvements.
February 20, 2022
1.8.5

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]

Patch Changes

  • e1fe48cbe Thanks @TimKolberger! - Bumped patch version for every package to fix release process. Root cause was a bug in our CI configuration.
  • Updated dependencies [e1fe48cbe]