Skip to content

Bump the dependencies group with 8 updates #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dependabot wants to merge 1 commit into from
Closed

Bump the dependencies group with 8 updates #131

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 31, 2025 •
edited
Loading

Bumps the dependencies group with 8 updates:

Package From To
@chakra-ui/react 2.10.7 3.15.0
@next/mdx 14.2.26 15.2.4
date-fns 3.6.0 4.1.0
framer-motion 11.18.2 12.6.2
next 14.2.26 15.2.4
react 18.3.1 19.1.0
@types/react 18.3.20 19.0.12
react-dom 18.3.1 19.1.0

Updates @chakra-ui/react from 2.10.7 to 3.15.0

Release notes

Sourced from @​chakra-ui/react's releases.

@​chakra-ui/react@​3.15.0

Minor Changes

  • 2f4ea3b Thanks @​segunadebayo! - - useMediaQuery: Fix type signature to allow skipping the second argument

    • RadioCard: Fix accessibility issue due to html structure

    • Slider

      • Add support for origin: end to align the thumb to the end of the track.
      • Expose thumbSize as CSS variables in the root element. Can be useful for styling the slider.

    • Menu

      • Added onSelect event to the Menu.Item component.
      • Ensure menu items have unique IDs to improve accessibility and HTML validation.

@​chakra-ui/react@​3.14.2

Patch Changes

@​chakra-ui/react@​3.14.1

Patch Changes

  • 0eb769e Thanks @​segunadebayo! - - System: Fix issue where output of <system>.css(...) from Chakra UI can't be assigned to Interpolation<Theme> from @emotion/react.

    • General: Bump @ark-ui/react to latest version.

@​chakra-ui/react@​3.14.0

Minor Changes

  • 354eaa6 Thanks @​segunadebayo! - Improve render performance by upgrading to the latest Ark UI v5.

    This brings a 1.5x–4x performance improvements across components. Learn more from the Ark UI v5 changelog.

@​chakra-ui/react@​3.13.0

... (truncated)

Changelog

Sourced from @​chakra-ui/react's changelog.

3.15.0

Minor Changes

  • 2f4ea3b Thanks @​segunadebayo! - - useMediaQuery: Fix type signature to allow skipping the second argument

    • RadioCard: Fix accessibility issue due to html structure

    • Slider

      • Add support for origin: end to align the thumb to the end of the track.
      • Expose thumbSize as CSS variables in the root element. Can be useful for styling the slider.

    • Menu

      • Added onSelect event to the Menu.Item component.
      • Ensure menu items have unique IDs to improve accessibility and HTML validation.

3.14.2

Patch Changes

3.14.1

Patch Changes

  • 0eb769e Thanks @​segunadebayo! - - System: Fix issue where output of <system>.css(...) from Chakra UI can't be assigned to Interpolation<Theme> from @emotion/react.

    • General: Bump @ark-ui/react to latest version.

3.14.0

Minor Changes

  • 354eaa6 Thanks @​segunadebayo! - Improve render performance by upgrading to the latest Ark UI v5.

    This brings a 1.5x–4x performance improvements across components. Learn more from the

... (truncated)

Commits

Updates @next/mdx from 14.2.26 to 15.2.4

Release notes

Sourced from @​next/mdx's releases.

v15.2.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Match subrequest handling for edge and node (#77474)
  • exclude images and static media from dev origin check (#77417)
  • ensure /__next middleware URLs are included in the origin check (#77416)
  • remove direct ip/port bypass in dev origin check (#77414)
  • switch development origin verification to be opt-in rather than opt-out (#77395)

Credits

Huge thanks to @​ijjk and @​ztanner for helping!

v15.2.3

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary. This release contains a security patch for CVE-2025-29927.

Core Changes

  • Update default allowed origins list (#77212)
  • unify allowed origin detection handling (#77053)
  • Add dev warning for cross-origin and stabilize allowedDevOrigins (#77044)
  • Ensure deploymentId is used for CSS preloads (#77210)
  • Update middleware request header (#77201)
  • [metadata] remove the default segement check for metadata rendering (#77119)
  • [ts-hint] fix vscode type hint plugin enabling (#77099)
  • [metadata] re-insert icons to head for streamed metadata (#76915)

Credits

Huge thanks to @​ijjk, @​ztanner, and @​huozhi for helping!

v15.2.2

Core Changes

  • [dev-overlay] fix styling on overflow error messages, add button hover state: #76771
  • Fix: respond 405 status code on OPTIONS request to SSG page: #76767
  • [dev-overlay] Always show relative paths: #76742
  • [metadata] remove the duplicate metadata in the error boundary: #76791
  • Upgrade React from d55cc79b-20250228 to 443b7ff2-20250303: #76804
  • [dev-overlay] Ignore animations on page load: #76834
  • fix: remove useless set-cookie in action-handler: #76839
  • Turbopack: handle task cancelation: #76831
  • Upgrade React from 443b7ff2-20250303 to e03ac20f-20250305: #76842

... (truncated)

Commits

Updates date-fns from 3.6.0 to 4.1.0

Release notes

Sourced from date-fns's releases.

v4.1.0

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

  • Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

  • Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

v4.0.0

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @​kossnocorp

Added

  • Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.

  • All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:

    import { addDays, startOfDay } from "date-fns";
import { tz } from "@date-fns/tz";
startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
//=> "2024-09-16T00:00:00.000+08:00"

    In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

  • The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

    The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

    In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.

    clamp(Date.now(), {
  start: new TZDate(start, "Asia/Singapore"),
  end: new UTCDate(),

... (truncated)

Changelog

Sourced from date-fns's changelog.

v4.1.0 - 2024-09-17

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

  • Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

  • Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

v4.0.0 - 2024-09-16

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @​kossnocorp

Added

  • Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.

  • All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:

    import { addDays, startOfDay } from "date-fns";
import { tz } from "@date-fns/tz";
startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
//=> "2024-09-16T00:00:00.000+08:00"

    In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

  • The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

    The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

    In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.

    clamp(Date.now(), {

... (truncated)

Commits
  • 313b902 Fix v4.1.0 change log entry
  • 26cd336 Promote to v4.1.0
  • 97b53b9 Cover time zone edge cases
  • 59b7563 Add missing time zone support to format, formatISO, formatISO9075, formatRela...
  • 0121164 Prevent constructFrom from throwing an error on null
  • bd87ef5 Update @​date-fns/docs
  • 99b4e67 Prepare v4.0
  • 8df1706 Rewrite the time zones doc
  • e351977 Promote to v4.0.0-beta.1
  • 8523656 Fix scripts/test/types.sh
  • Additional commits viewable in compare view

Updates framer-motion from 11.18.2 to 12.6.2

Changelog

Sourced from framer-motion's changelog.

[12.6.2] 2025-03-26

Fixed

  • Fixing hardware acceleration for non-transform values when a motion component has a defined transformTemplate.

[12.6.1] 2025-03-26

Fixed

  • Reverting pointer capture for press gesture.

[12.6.0] 2025-03-25

Changed

  • Renamed view to animateView.

Added

  • New interrupt: "wait" mode as animateView default.

[12.5.0] 2025-03-11

Added

  • Added motionValue to vanilla JS entrypoint.

Removed

  • Removed framer-motion-3d package.

[12.4.13] 2025-03-11

Fixed

  • Fixed reading initial transform values from elements.

[12.4.12] 2025-03-11

Fixed

  • Removed pointer capture from pan and drag gestures.

[12.4.11] 2025-03-10

Fixed

  • Preventing flattening of scroll animations when type or ease are explicitly set.

... (truncated)

Commits

Updates next from 14.2.26 to 15.2.4

Release notes

Sourced from next's releases.

v15.2.4

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Match subrequest handling for edge and node (#77474)
  • exclude images and static media from dev origin check (#77417)
  • ensure /__next middleware URLs are included in the origin check (#77416)
  • remove direct ip/port bypass in dev origin check (#77414)
  • switch development origin verification to be opt-in rather than opt-out (#77395)

Credits

Huge thanks to @​ijjk and @​ztanner for helping!

v15.2.3

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary. This release contains a security patch for CVE-2025-29927.

Core Changes

  • Update default allowed origins list (#77212)
  • unify allowed origin detection handling (#77053)
  • Add dev warning for cross-origin and stabilize allowedDevOrigins (#77044)
  • Ensure deploymentId is used for CSS preloads (#77210)
  • Update middleware request header (#77201)
  • [metadata] remove the default segement check for metadata rendering (#77119)
  • [ts-hint] fix vscode type hint plugin enabling (#77099)
  • [metadata] re-insert icons to head for streamed metadata (#76915)

Credits

Huge thanks to @​ijjk, @​ztanner, and @​huozhi for helping!

v15.2.2

Core Changes

  • [dev-overlay] fix styling on overflow error messages, add button hover state: #76771
  • Fix: respond 405 status code on OPTIONS request to SSG page: #76767
  • [dev-overlay] Always show relative paths: #76742
  • [metadata] remove the duplicate metadata in the error boundary: #76791
  • Upgrade React from d55cc79b-20250228 to 443b7ff2-20250303: #76804
  • [dev-overlay] Ignore animations on page load: #76834
  • fix: remove useless set-cookie in action-handler: #76839
  • Turbopack: handle task cancelation: #76831
  • Upgrade React from 443b7ff2-20250303 to e03ac20f-20250305: #76842

... (truncated)

Commits

Updates react from 18.3.1 to 19.1.0

Release notes

Sourced from react's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
  • Added support for <script> and \<template> tags to be nested within <select> tags. #31837
  • Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
  • Fixed an issue where pending chunks were counted twice. #31833
  • Added support for streaming in edge environments #31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a [email protected] release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

... (truncated)

Changelog

Sourced from react's changelog.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
  • Added support for <script> and \<template> tags to be nested within <select> tags. #31837
  • Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
  • Fixed an issue where pending chunks were counted twice. #31833
  • Added support for streaming in edge environments #31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

... (truncated)

Commits

Updates @types/react from 18.3.20 to 19.0.12

Commits

Updates react-dom from 18.3.1 to 19.1.0

Release notes

Sourced from react-dom's releases.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for consistent task yielding. #31785
  • Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #32528
  • Fixed component name resolution for Portal #32640
  • Added support for beforetoggle and toggle events on the dialog element. #32479 #32479

React DOM

  • Fixed double warning when the href attribute is an empty string #31783
  • Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #32321
  • Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #32250
  • Added support for <script> and \<template> tags to be nested within <select> tags. #31837
  • Fixed responsive images to be preloaded as HTML instead of headers #32445

use-sync-external-store

  • Added exports field to package.json for use-sync-external-store to support various entrypoints. #25231

React Server Components

  • Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #31724
  • Fixed an issue where streams would hang when receiving new chunks after a global error #31840, #31851
  • Fixed an issue where pending chunks were counted twice. #31833
  • Added support for streaming in edge environments #31852
  • Added support for sending custom error names from a server so that they are available in the client for console replaying. #32116
  • Updated the server component wire format to remove IDs for hints and console.log because they have no return value #31671
  • Exposed registerServerReference in client builds to handle server references in different environments. #32534
  • Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #31725, #32132, #31799, #32294, #31741

19.0.0 (December 5, 2024)

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 19 release post and React 19 upgrade guide for more information.

Note: To help make the upgrade to React 19 easier, we’ve published a [email protected] release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19. We recommend upgrading to React 18.3.1 first to help identify any issues before upgrading to React 19.

... (truncated)

Changelog

Sourced from react-dom's changelog.

19.1.0 (March 28, 2025)

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

  • An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
  • The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #29923, #32353, #30306, #32538, #32529, #32538

React

  • Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #32069, #32163, #32224, #32252
  • Reduced unnecessary client rendering through improved hydration scheduling #31751
  • Increased priority of client rendered Suspense boundaries #31776
  • Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #31620
  • Reduced garbage collection pressure by improving Suspense boundary retries. #31667
  • Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #31526
  • Fixed a regression causing key warnings for flattened positional children in development mode. #32117
  • Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #32001
  • Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #32355
  • Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #32200
  • Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #31808
  • Improve passive effect scheduling for co...

    Description has been truncated

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Mar 31, 2025
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/dependencies-36d0ef2cdf branch from 0008ddd to a4ab1f5 Compare March 31, 2025 15:09
@dependabot
Bump the dependencies group with 8 updates
91ea313 
Bumps the dependencies group with 8 updates:

| Package | From | To |
| --- | --- | --- |
| [@chakra-ui/react](https://github.com/chakra-ui/chakra-ui/tree/HEAD/packages/react) | `2.10.7` | `3.15.0` |
| [@next/mdx](https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx) | `14.2.26` | `15.2.4` |
| [date-fns](https://github.com/date-fns/date-fns) | `3.6.0` | `4.1.0` |
| [framer-motion](https://github.com/motiondivision/motion) | `11.18.2` | `12.6.2` |
| [next](https://github.com/vercel/next.js) | `14.2.26` | `15.2.4` |
| [react](https://github.com/facebook/react/tree/HEAD/packages/react) | `18.3.1` | `19.1.0` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `18.3.20` | `19.0.12` |
| [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) | `18.3.1` | `19.1.0` |


Updates `@chakra-ui/react` from 2.10.7 to 3.15.0
- [Release notes](https://github.com/chakra-ui/chakra-ui/releases)
- [Changelog](https://github.com/chakra-ui/chakra-ui/blob/main/packages/react/CHANGELOG.md)
- [Commits](https://github.com/chakra-ui/chakra-ui/commits/@chakra-ui/[email protected]/packages/react)

Updates `@next/mdx` from 14.2.26 to 15.2.4
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v15.2.4/packages/next-mdx)

Updates `date-fns` from 3.6.0 to 4.1.0
- [Release notes](https://github.com/date-fns/date-fns/releases)
- [Changelog](https://github.com/date-fns/date-fns/blob/main/CHANGELOG.md)
- [Commits](date-fns/date-fns@v3.6.0...v4.1.0)

Updates `framer-motion` from 11.18.2 to 12.6.2
- [Changelog](https://github.com/motiondivision/motion/blob/main/CHANGELOG.md)
- [Commits](motiondivision/motion@v11.18.2...v12.6.2)

Updates `next` from 14.2.26 to 15.2.4
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.26...v15.2.4)

Updates `react` from 18.3.1 to 19.1.0
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.1.0/packages/react)

Updates `@types/react` from 18.3.20 to 19.0.12
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `react-dom` from 18.3.1 to 19.1.0
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.1.0/packages/react-dom)

---
updated-dependencies:
- dependency-name: "@chakra-ui/react"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: "@next/mdx"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: date-fns
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: framer-motion
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: next
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: react
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: "@types/react"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: react-dom
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/dependencies-36d0ef2cdf branch from a4ab1f5 to 91ea313 Compare April 2, 2025 00:01
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github May 1, 2025

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this May 1, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/dependencies-36d0ef2cdf branch May 1, 2025 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant