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

chore(deps): update dependency tailwindcss to v3.4.17 #702

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tailwindcss (source) 3.4.9 -> 3.4.17 age adoption passing confidence

Release Notes

tailwindlabs/tailwindcss (tailwindcss)

v3.4.17

Compare Source

Fixed

v3.4.16

Compare Source

Fixed
  • Ensure the TypeScript types for PluginsConfig allow undefined values (#​14668)

Changed

v3.4.15

Compare Source

  • Bump versions for security vulnerabilities (#​14697)
  • Ensure the TypeScript types for the boxShadow theme configuration allows arrays (#​14856)
  • Set fallback for opacity variables to ensure setting colors with the selection:* variant works in Chrome 131 (#​15003)

v3.4.14

Compare Source

Fixed
  • Don't set display: none on elements that use hidden="until-found" (#​14625)

v3.4.13

Compare Source

Fixed
  • Improve source glob verification performance (#​14481)

v3.4.12

Compare Source

Fixed
  • Ensure using @apply with utilities that use @defaults works with rules defined in the base layer when using optimizeUniversalDefaults (#​14427)

v3.4.11

Compare Source

Fixed
  • Allow anchor-size(…) in arbitrary values (#​14393)

v3.4.10

Compare Source

Fixed
  • Bump versions of plugins in the Standalone CLI (#​14185)

v3.4.9

Compare Source

Fixed
  • No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Compare Source

Fixed
  • Fix minification when using nested CSS (#​14105)
  • Warn when broad glob patterns are used in the content configuration (#​14140)

v3.4.7

Compare Source

Fixed
  • Fix class detection in Slim templates with attached attributes and ID (#​14019)
  • Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#​14037)

v3.4.6

Compare Source

Fixed
  • Fix detection of some utilities in Slim/Pug templates (#​14006)
Changed
  • Loosen :is() wrapping rules when using an important selector (#​13900)

v3.4.5

Compare Source

Fixed
  • Disable automatic var() injection for anchor properties (#​13826)
  • Use no value instead of blur(0px) for backdrop-blur-none and blur-none utilities (#​13830)
  • Add .mts and .cts config file detection (#​13940)
  • Don't generate utilities like px-1 unnecessarily when using utilities like px-1.5 (#​13959)
  • Always generate -webkit-backdrop-filter for backdrop-* utilities (#​13997)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Jan 30, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.6.0" from the root project
npm ERR!   peer eslint@">=8.40.0" from @antfu/[email protected]
npm ERR!   node_modules/@antfu/eslint-config
npm ERR!     dev @antfu/eslint-config@"^2.0.0" from the root project
npm ERR!   22 more (@eslint-community/eslint-utils, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8" from [email protected]
npm ERR! node_modules/eslint-plugin-react
npm ERR!   dev eslint-plugin-react@"^7.33.2" from the root project
npm ERR!   peerOptional eslint-plugin-react@"^7.33.2" from @antfu/[email protected]
npm ERR!   node_modules/@antfu/eslint-config
npm ERR!     dev @antfu/eslint-config@"^2.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8" from [email protected]
npm ERR!   node_modules/eslint-plugin-react
npm ERR!     dev eslint-plugin-react@"^7.33.2" from the root project
npm ERR!     peerOptional eslint-plugin-react@"^7.33.2" from @antfu/[email protected]
npm ERR!     node_modules/@antfu/eslint-config
npm ERR!       dev @antfu/eslint-config@"^2.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-30T15_02_52_884Z-debug-0.log

Copy link

vercel bot commented Jan 30, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
my-next ❌ Failed (Inspect) Jan 30, 2025 3:04pm

Copy link

stackblitz bot commented Jan 30, 2025

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants