An open index of dependabot pull requests across open source projects.

Bump the production-dependencies group with 18 updates

Merged
Number: #1
Type: Pull Request
State: Merged
Author: dependabot[bot] dependabot[bot]
Association: Contributor
Comments: 0
Created: August 31, 2025 at 04:56 AM UTC
(10 days ago)
Updated: August 31, 2025 at 05:05 AM UTC
(10 days ago)
Merged: August 31, 2025 at 05:05 AM UTC
(10 days ago)
by codeMonkeyHopeful
Time to Close: 10 minutes
Labels:
dependencies javascript
Description:

Bumps the production-dependencies group with 18 updates:

Package From To
@types/node 18.15.0 24.3.0
clsx 1.2.1 2.1.1
date-fns 2.30.0 4.1.0
framer-motion 10.18.0 12.23.12
lucide-react 0.469.0 0.542.0
react 19.0.0 19.1.1
@types/react 18.3.3 19.1.12
react-dom 19.0.0 19.1.1
@types/react-dom 18.0.11 19.1.9
react-icons 4.12.0 5.5.0
rehype-autolink-headings 6.1.1 7.1.0
rehype-pretty-code 0.9.11 0.14.1
rehype-slug 5.1.0 6.0.0
remark-gfm 3.0.1 4.0.1
shiki 0.14.7 3.12.0
sugar-high 0.7.5 0.9.3
tailwind-merge 2.6.0 3.3.1
typescript 5.5.2 5.9.2

Updates @types/node from 18.15.0 to 24.3.0

Commits

Updates clsx from 1.2.1 to 2.1.1

Release notes

Sourced from clsx's releases.

v2.1.1

Patches

  • (types) Include bigint in ClassValue type: (#96): 3d960ab Accommodates recent @types/react changes to ReactNode. Thank you @​ViliamKopecky~!

Chores

  • Add licenses.dev badge: 684509c This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

Full Changelog: https://github.com/lukeed/clsx/compare/v2.1.0...v2.1.1

v2.1.0

Features

  • Add new clsx/lite submodule for string-only usage: 1a49142

    This is a 140b version of clsx that is ideal for Tailwind and/or React contexts, which typically follow this clsx usage pattern:

    clsx('foo bar', props.maybe && 'conditional classes', props.className);
    

    Important: This clsx/lite module ignores all non-string arguments and is therefore not a 1:1 replacement for clsx itself!

    import { clsx } from 'clsx';
    import { clsx as lite } from 'clsx/lite';
    

    // strings-only usage is identical
    clsx('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"
    lite('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"

    // clsx/lite ignores all non-strings
    clsx('foo', { a: true, b: false, c: true }); //=> "foo a c"
    lite('foo', { a: true, b: false, c: true }); //=> "foo"


Full Changelog: https://github.com/lukeed/clsx/compare/v2.0.1...v2.1.0

v2.0.1

Patches

  • (perf) Cache arguments.length & array.length for 6% performance gain (#26): deff09b

... (truncated)

Commits

Updates date-fns from 2.30.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 10.18.0 to 12.23.12

Changelog

Sourced from framer-motion's changelog.

[12.23.12] 2025-07-29

Added

  • Exporting internal APIs for use in view animations.

[12.23.11] 2025-07-28

Added

  • Children of variants with delayChildren: stagger() will now be staggered correctly alongside their newly-entering siblings.

[12.23.10] 2025-07-28

Fixed

  • Fixed shared layout animation in situations where no motion components have re-rendered between shared element switching.

[12.23.9] 2025-07-24

Changed

  • Removing redundant renderRequest MotionValue lifecycle.

[12.23.8] 2025-07-24

Fixed

  • Ensuring that when an animation is skipped via duration = 0 that we also set type = "keyframes" so that duration takes effect.

[12.23.7] 2025-07-23

Fixed

  • springValue cleanup.
  • Removed additional removeNode from AnimatePresence when using popLayout.

[12.23.6] 2025-07-11

Changed

  • Added explainer for reduced motion warning.
  • Refactored motion component creation to remove indirection.

[12.23.5] 2025-07-11

Fixed

  • Fix animation timings within dynamically-generated popups.

... (truncated)

Commits

Updates lucide-react from 0.469.0 to 0.542.0

Release notes

Sourced from lucide-react's releases.

Version 0.542.0

What's Changed

New Contributors

Full Changelog: https://github.com/lucide-icons/lucide/compare/0.541.0...0.542.0

Version 0.541.0

What's Changed

Full Changelog: https://github.com/lucide-icons/lucide/compare/0.540.0...0.541.0

Version 0.540.0

What's Changed

Full Changelog: https://github.com/lucide-icons/lucide/compare/0.539.0...0.540.0

Version 0.539.0

What's Changed

Full Changelog: https://github.com/lucide-icons/lucide/compare/0.538.0...0.539.0

Version 0.538.0

What's Changed

... (truncated)

Commits

Updates react from 19.0.0 to 19.1.1

Release notes

Sourced from react's releases.

19.1.1 (July 28, 2025)

React

  • Fixed Owner Stacks to work with ES2015 function.name semantics (#33680 by @​hoxyq)

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
Changelog

Sourced from react's changelog.

19.1.1 (July 28, 2025)

React

  • Fixed Owner Stacks to work with ES2015 function.name semantics (#33680 by @​hoxyq)

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 Compiler 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

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

... (truncated)

Commits

Updates @types/react from 18.3.3 to 19.1.12

Commits

Updates react-dom from 19.0.0 to 19.1.1

Release notes

Sourced from react-dom's releases.

19.1.1 (July 28, 2025)

React

  • Fixed Owner Stacks to work with ES2015 function.name semantics (#33680 by @​hoxyq)

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
Changelog

Sourced from react-dom's changelog.

19.1.1 (July 28, 2025)

React

  • Fixed Owner Stacks to work with ES2015 function.name semantics (#33680 by @​hoxyq)

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 Compiler 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

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

... (truncated)

Commits
Package Dependencies
Ecosystem:
npm
Version Change:
0.469.0 → 0.542.0
Update Type:
Minor
Package:
@types/node
Ecosystem:
npm
Version Change:
18.15.0 → 24.3.0
Update Type:
Major
Ecosystem:
npm
Version Change:
18.3.3 → 19.1.12
Update Type:
Major
Package:
react-dom
Ecosystem:
npm
Version Change:
19.0.0 → 19.1.1
Update Type:
Minor
Ecosystem:
npm
Version Change:
18.0.11 → 19.1.9
Update Type:
Major
Package:
typescript
Ecosystem:
npm
Version Change:
5.5.2 → 5.9.2
Update Type:
Minor
Ecosystem:
npm
Version Change:
10.18.0 → 12.23.12
Update Type:
Major
Package:
react
Ecosystem:
npm
Version Change:
19.0.0 → 19.1.1
Update Type:
Minor
Ecosystem:
npm
Version Change:
2.6.0 → 3.3.1
Update Type:
Major
Package:
date-fns
Ecosystem:
npm
Version Change:
2.30.0 → 4.1.0
Update Type:
Major
Package:
clsx
Ecosystem:
npm
Version Change:
1.2.1 → 2.1.1
Update Type:
Major
Package:
react-icons
Ecosystem:
npm
Version Change:
4.12.0 → 5.5.0
Update Type:
Major
Package:
shiki
Ecosystem:
npm
Version Change:
0.14.7 → 3.12.0
Update Type:
Major
Ecosystem:
npm
Version Change:
0.9.11 → 0.14.1
Update Type:
Minor
Package:
remark-gfm
Ecosystem:
npm
Version Change:
3.0.1 → 4.0.1
Update Type:
Major
Ecosystem:
npm
Version Change:
6.1.1 → 7.1.0
Update Type:
Major
Package:
sugar-high
Ecosystem:
npm
Version Change:
0.7.5 → 0.9.3
Update Type:
Minor
Package:
rehype-slug
Ecosystem:
npm
Version Change:
5.1.0 → 6.0.0
Update Type:
Major
Technical Details
ID: 6022941
UUID: 2787363263
Node ID: PR_kwDOPnMIoM6mI8m_
Host: GitHub
Repository: codeMonkeyHopeful/placeholder.github.io
Merge State: Unknown