[Snyk] Upgrade tailwindcss from 3.3.2 to 4.1.3 #785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade tailwindcss from 3.3.2 to 4.1.3.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 91 versions ahead of your current version.
The recommended version was released 25 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-WS-7266574
SNYK-JS-BRACES-6838727
SNYK-JS-MICROMATCH-6838728
SNYK-JS-NEXT-8186172
SNYK-JS-NEXT-8520073
SNYK-JS-INFLIGHT-6095116
SNYK-JS-NANOID-8492085
SNYK-JS-NEXT-6032387
SNYK-JS-NEXT-9508709
SNYK-JS-POSTCSS-5926692
SNYK-JS-POSTCSS-5926692
Release notes
Package name: tailwindcss
Fixed
--value(…)
(#17464)%w
syntax in Slim templates (#17557)Fixed
@ layer base
to polyfill@ property
(#17506)drop-shadow-*
utilities that are defined with multiple shadows (#17515)@ tailwind utilities
are processed (#17514)color-mix(…)
polyfill creates fallbacks even when using colors that cannot be statically analyzed (#17513)@ tailwindcss/vite
and@ tailwindcss/postscss
(especially on Windows) (#17511)Fixed
@ source inline(…)
brace expansion (#17491)@ import
and body-less@ layer
(#17493)@ tailwindcss/cli
does not contain an import forjiti
(#17502)Added
details-content
variant (#15319)inverted-colors
variant (#11693)noscript
variant (#11929, #17431)items-baseline-last
andself-baseline-last
utilities (#13888, #17476)pointer-none
,pointer-coarse
, andpointer-fine
variants (#16946)any-pointer-none
,any-pointer-coarse
, andany-pointer-fine
variants (#16941)user-valid
anduser-invalid
variants (#12370)wrap-anywhere
,wrap-break-word
, andwrap-normal
utilities (#12128)@ source inline(…)
and@ source not inline(…)
(#17147)@ source not "…"
(#17255)text-shadow-*
utilities (#17389)mask-*
utilities (#17134)bg-{position,size}-*
utilities for arbitrary values (#17432)shadow-*/<alpha>
,inset-shadow-*/<alpha>
,drop-shadow-*/<alpha>
, andtext-shadow-*/<alpha>
utilities to control shadow opacity (#17398, #17434)drop-shadow-<color>
utilities (#17434)Fixed
@ source
directives (#17391)@ tailwindcss/cli
(#17255)content
rules in legacy JavaScript configuration (#17255)@("@")md:…
as@ md:…
in Razor files (#17427)--theme(…)
function still resolves to the CSS variables when using legacy JS plugins (#17458)Changed
node_modules
by default (can be overridden by@ source …
rules) (#17255)@ source
rules that include file extensions or point insidenode_modules/
folders no longer consider your.gitignore
rules (#17255)bg-{left,right}-{top,bottom}
in favor ofbg-{top,bottom}-{left,right}
utilities (#17378)object-{left,right}-{top,bottom}
in favor ofobject-{top,bottom}-{left,right}
utilities (#17437)Fixed
Added
--value('…')
and--modifier('…')
(#17304)Fixed
(
in Pug (#17320)@ keyframes
for theme animations are emitted if they are referenced following a comma (#17352)Slim
templates embedded in Ruby files (#17336)--spacing(--value(integer, number))
is used (#17308)::-webkit-details-marker
pseudo tomarker
variant (#17362)Fixed
-bg-conic-*
utilities (#17174)border-[12px_4px]
being interpreted as aborder-color
instead of aborder-width
(#17248)<template lang="…">
in Vue files (#17252)--value(…)
or--modifier(…)
calls don't delete subsequent declarations (#17273)(
in Slim (#17278)PluginUtils
fromtailwindcss/plugin
for compatibility with v3 (#17299)line-height: initial
from Preflight (#15212)Changed
--theme(…)
function now returns CSS variables from your theme variables unless used inside positions where CSS variables are invalid (e.g. inside@ media
queries) (#17036)Fixed
${
(#17142).
character (#17153)Fixed
.node
and.wasm
files are not scanned for utilities (#17123)Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
Summary by Sourcery
Upgrade Tailwind CSS from version 3.3.2 to 4.1.3, addressing multiple security vulnerabilities
New Features:
Bug Fixes: