Update tailwindcss 3.4.3 → 3.4.12 (patch) #3244
Closed
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ tailwindcss (3.4.3 → 3.4.12) · Repo · Changelog
Release Notes
3.4.12
3.4.11
3.4.10
3.4.9
3.4.8
3.4.7
3.4.6
3.4.5
3.4.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 42 commits:
3.4.12
Insert `@defaults` at start of stylesheet (#14427)
3.4.11
update changelog
Allow `anchor-size(…)` in arbitrary values (#14393)
3.4.10
Bump versions of plugins in the Standalone CLI (#14185)
3.4.9
Don't warn about broad globs in vendor folders (#14147)
3.4.8
rename `master` to `main`
Warn when broad glob patterns are used in the content configuration (#14140)
Bump to latest cssnano v6 (#14105)
Automate checksum generation for standalone CLI (#14081)
Update version in package.json
Add missing heading to changelog
Update changelog for v3.4.7
Update CHANGELOG.md
Normalize attribute selector for `data-*` and `aria-*` modifiers (#14037)
Print eventual lightning CSS parsing errors when the CSS matcher fail (#14034)
Fix class detection in Slim templates with attached attributes and IDs (#14019)
Update changelog
Loosen :is() wrapping rules in applyImportantSelector for more readable output. (#13900)
3.4.6
Update changelog
Fix extracting utilities from slim/pug templates (#14006)
Update runner image
3.4.5
Always generate -webkit-backdrop-filter property (#13997)
Avoid over-extracting utilities from candidates with decimal values (#13959)
Add `.mts` and `.cts` config file detection (#13940)
refactor(util): code refactor (#13872)
fix: typo (#13864)
Use no value instead of `blur(0px)` for `backdrop-blur-none` and `blur-none` utilities (#13830)
Disable automatic `var()` injection for anchor properties (#13826)
3.4.4
Update changelog
Bump deps (#13797)
Update browserslist database (#13792)
[v3] Support negative values for `{col,row}-{start,end}` utilities (#13781)
Don't prefix classes in arbitrary values of `has-*`, `group-has-*`, and `peer-has-*` variants (#13770)
Fix multiple <alpha-value> in color definitions (#13740)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands