Skip to content
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.

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

deps(example): bump the dependencies group across 1 directory with 7 updates #3032

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 31, 2025

Bumps the dependencies group with 7 updates in the /examples/nextjs-react-hook-form directory:

Package From To
lucide-react 0.473.0 0.474.0
next 15.1.5 15.1.6
tailwind-merge 2.6.0 3.0.1
@types/react 19.0.7 19.0.8
@typescript-eslint/parser 8.21.0 8.22.0
eslint-config-next 15.1.5 15.1.6
tailwindcss 3.4.17 4.0.1

Updates lucide-react from 0.473.0 to 0.474.0

Release notes

Sourced from lucide-react's releases.

New icons 0.474.0

Modified Icons 🔨

Commits

Updates next from 15.1.5 to 15.1.6

Release notes

Sourced from next's releases.

v15.1.6

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

Core Changes

  • fix: don't memory-leak promises passed to waitUntil (#75041)
  • backport: fix prerender issue with intercepting routes + generateStaticParams (#75170)

Credits

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

Commits

Updates tailwind-merge from 2.6.0 to 3.0.1

Release notes

Sourced from tailwind-merge's releases.

v3.0.1

Bug Fixes

  • Update info about supported Tailwind CSS version in README by @​dcastil in b9c136d
  • Update incorrect link in v3 changelog by @​dcastil in e22885e

Full Changelog: dcastil/tailwind-merge@v3.0.0...v3.0.1

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.0

Tailwind CSS v4 is here and it's time to upgrade tailwind-merge to support it. tailwind-merge v3.0.0 is more accurate than ever and follows the Tailwind CSS spec more closely than in v2. That is thanks to Tailwind CSS v4 being more consistent than ever.

This release drops support for Tailwind CSS v3 and in turn adds support for Tailwind CSS v4. That means you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together. All breaking changes are related to the Tailwind CSS v4 support.

Check out the migration guide and if you have any questions, feel free to create an issue.

Breaking Changes

New Features

Bug Fixes

Documentation

Full Changelog: dcastil/tailwind-merge@v2.6.0...v3.0.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

Commits
  • 493fa8c v3.0.1
  • b9c136d update info about supported Tailwind CSS version in README
  • e22885e fix link in v3 changelog
  • 7378c16 v3.0.0
  • a00a8e6 change label added to new issues to context-v3
  • 7c8c994 Merge pull request #518 from dcastil/breaking-feature/513/tailwind-css-v4-sup...
  • 7f043a6 small tweaks
  • 1950ab6 add migration doc for tailwind-merge v3
  • ef00078 add removed custom separator support to breaking changes in v3 changelog
  • 752b103 remove separator from docs
  • Additional commits viewable in compare view

Updates @types/react from 19.0.7 to 19.0.8

Commits

Updates @typescript-eslint/parser from 8.21.0 to 8.22.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.22.0

8.22.0 (2025-01-27)

🚀 Features

  • parser: add standalone isolatedDeclarations option (#10499)

🩹 Fixes

  • eslint-plugin: [prefer-nullish-coalescing] doesn't report on ternary but on equivalent || (#10517)
  • eslint-plugin: [no-duplicate-type-constituents] handle nested types (#10638)
  • eslint-plugin: [no-shadow] don't report unnecessarily on valid ways of using module augmentation (#10616)
  • eslint-plugin: [no-extraneous-class] handle accessor keyword (#10678)
  • eslint-plugin: [prefer-readonly] autofixer doesn't add type to property that is mutated in the constructor (#10552)
  • eslint-plugin: [no-unnecessary-template-expression] handle template literal type (#10612)
  • type-utils: support matching intersection types in TypeOrValueSpecifier with a PackageSpecifier (#10667)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.22.0 (2025-01-27)

🚀 Features

  • parser: add standalone isolatedDeclarations option (#10499)

❤️ Thank You

  • Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

Commits

Updates eslint-config-next from 15.1.5 to 15.1.6

Release notes

Sourced from eslint-config-next's releases.

v15.1.6

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

Core Changes

  • fix: don't memory-leak promises passed to waitUntil (#75041)
  • backport: fix prerender issue with intercepting routes + generateStaticParams (#75170)

Credits

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

Commits

Updates tailwindcss from 3.4.17 to 4.0.1

Release notes

Sourced from tailwindcss's releases.

v4.0.1

Added

  • Include :open pseudo-class in existing open variant (#15349)

Fixed

  • Remove invalid min-w/h-none utilities (#15845)
  • Discard CSS variable shorthand utilities that don't use valid CSS variables (#15738)
  • Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#15921)
  • Ensure font-size utilities with unknown modifier don't generate CSS (#15921)
  • Don’t suggest font weight utilities more than once (#15857)
  • Suggest container query variants (#15857)
  • Disable bare value suggestions when not using the --spacing variable (#15857)
  • Ensure suggested classes are properly sorted (#15857)
  • Don’t look at .gitignore files outside initialized repos (#15941)
  • Find utilities when using the Svelte class shorthand syntax across multiple lines (#15974)
  • Find utilities when using the Angular class shorthand syntax (#15974)
  • Find utilities when using functions inside arrays (#15974)
  • Ensure that @tailwindcss/browser does not pollute the global namespace (#15978)
  • Ensure that tailwind-merge is not scanned when using the Vite plugin (#16005)
  • Ensure CSS theme variables are available within shadow roots (#15975)
  • Fix crash when project lives in the / directory (#15988)
  • Ensure custom variants have a non-empty selector list (#16009)
  • Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#15927)
  • Upgrade: Migrate leading-[1] to leading-none (#16004)
  • Upgrade: Do not migrate arbitrary leading utilities to bare values (#16004)

v4.0.0

Holy shit it's actually done — we just tagged Tailwind CSS v4.0.

Tailwind CSS v4.0 is an all-new version of the framework optimized for performance and flexibility, with a reimagined configuration and customization experience, and taking full advantage of the latest advancements the web platform has to offer.

  • New high-performance engine — where full builds are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
  • Designed for the modern web — built on cutting-edge CSS features like cascade layers, registered custom properties with @property, and color-mix().
  • Simplified installation — fewer dependencies, zero configuration, and just a single line of code in your CSS file.
  • First-party Vite plugin — tight integration for maximum performance and minimum configuration.
  • Automatic content detection — all of your template files are discovered automatically, with no configuration required.
  • Built-in import support — no additional tooling necessary to bundle multiple CSS files.
  • CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
  • CSS theme variables — all of your design tokens exposed as native CSS variables so you can access them anywhere.
  • Dynamic utility values and variants — stop guessing what values exist in your spacing scale, or extending your configuration for things like basic data attributes.
  • Modernized P3 color palette — a redesigned, more vivid color palette that takes full advantage of modern display technology.
  • Container queries — first-class APIs for styling elements based on their container size, no plugins required.
  • New 3D transform utilities — transform elements in 3D space directly in your HTML.
  • Expanded gradient APIs — radial and conic gradients, interpolation modes, and more.
  • @​starting-style support — a new variant you can use to create enter and exit transitions, without the need for JavaScript.
  • not-* variant — style an element only when it doesn't match another variant, custom selector, or media or feature query.

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.0.1] - 2025-01-29

Added

  • Include :open pseudo-class in existing open variant (#15349)

Fixed

  • Remove invalid min-w/h-none utilities (#15845)
  • Discard CSS variable shorthand utilities that don't use valid CSS variables (#15738)
  • Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#15921)
  • Ensure font-size utilities with unknown modifier don't generate CSS (#15921)
  • Don’t suggest font weight utilities more than once (#15857)
  • Suggest container query variants (#15857)
  • Disable bare value suggestions when not using the --spacing variable (#15857)
  • Ensure suggested classes are properly sorted (#15857)
  • Don’t look at .gitignore files outside initialized repos (#15941)
  • Find utilities when using the Svelte class shorthand syntax across multiple lines (#15974)
  • Find utilities when using the Angular class shorthand syntax (#15974)
  • Find utilities when using functions inside arrays (#15974)
  • Ensure that @tailwindcss/browser does not pollute the global namespace (#15978)
  • Ensure that tailwind-merge is not scanned when using the Vite plugin (#16005)
  • Ensure CSS theme variables are available within shadow roots (#15975)
  • Fix crash when project lives in the / directory (#15988)
  • Ensure custom variants have a non-empty selector list (#16009)
  • Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#15927)
  • Upgrade: Migrate leading-[1] to leading-none (#16004)
  • Upgrade: Do not migrate arbitrary leading utilities to bare values (#16004)

[4.0.0] - 2025-01-21

Added

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…updates

Bumps the dependencies group with 7 updates in the /examples/nextjs-react-hook-form directory:

| Package | From | To |
| --- | --- | --- |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `0.473.0` | `0.474.0` |
| [next](https://github.com/vercel/next.js) | `15.1.5` | `15.1.6` |
| [tailwind-merge](https://github.com/dcastil/tailwind-merge) | `2.6.0` | `3.0.1` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.0.7` | `19.0.8` |
| [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) | `8.21.0` | `8.22.0` |
| [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) | `15.1.5` | `15.1.6` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `3.4.17` | `4.0.1` |



Updates `lucide-react` from 0.473.0 to 0.474.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/0.474.0/packages/lucide-react)

Updates `next` from 15.1.5 to 15.1.6
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.1.5...v15.1.6)

Updates `tailwind-merge` from 2.6.0 to 3.0.1
- [Release notes](https://github.com/dcastil/tailwind-merge/releases)
- [Commits](dcastil/tailwind-merge@v2.6.0...v3.0.1)

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

Updates `@typescript-eslint/parser` from 8.21.0 to 8.22.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.22.0/packages/parser)

Updates `eslint-config-next` from 15.1.5 to 15.1.6
- [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.1.6/packages/eslint-config-next)

Updates `tailwindcss` from 3.4.17 to 4.0.1
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.0.1/packages/tailwindcss)

---
updated-dependencies:
- dependency-name: lucide-react
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: next
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: tailwind-merge
  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-patch
  dependency-group: dependencies
- dependency-name: "@typescript-eslint/parser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: eslint-config-next
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: tailwindcss
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner January 31, 2025 07:01
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 31, 2025
@dependabot dependabot bot requested review from blaine-arcjet and e-moran January 31, 2025 07:01
Copy link

trunk-io bot commented Jan 31, 2025

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

Copy link

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
License Policy Violation npm/[email protected]
  • License: CC-BY-SA-4.0 - Not allowed by license policy (package/dist/compiled/glob/LICENSE, package/dist/compiled/glob/LICENSE)
⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants