Update tailwindcss 3.3.2 → 3.3.3 (patch) #2582
Merged
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.3.2 → 3.3.3) · Repo · Changelog
Release Notes
3.3.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
3.3.3
Update changelog
Don’t error when a config file is missing
Don't prefix arbitrary classes in `peer`/`group` variants (#11454)
Make PostCSS plugin async to improve performance (#11548)
Allow variant to be an at-rule without a prelude (#11589)
Sort classes using position of first matching rule (#11504)
Reset dialog element styles (#11069)
Add `aria-busy` utility (#10966)
Make font settings propagate into buttons, inputs, etc. (#10940)
Ensure CI jobs don't run for longer than 15 minutes (#11496)
Escape animation names when prefixes contain special characters (#11470)
Move unknown pseudo elements outside of `:is` (#11345)
fixed a type in generateRules.js (#11264)
Ensure `repeating-conic-gradient` is detected as an image (#11180)
Fix parsing of `theme()` inside `calc()` when there are no spaces around operators (#11157)
Fix issues with some pseudo-elements (#11111)
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