Update @tailwindcss/postcss 4.1.12 → 4.1.14 (patch)#4
Closed
depfu[bot] wants to merge 1 commit intomainfrom
Closed
Update @tailwindcss/postcss 4.1.12 → 4.1.14 (patch)#4depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Author
|
Closed in favor of #5. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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/postcss (4.1.12 → 4.1.14)
Sorry, we couldn't find anything useful about this release.
✳️ tailwindcss (4.1.12 → 4.1.14) · Repo · Changelog
Release Notes
4.1.14
4.1.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 64 commits:
Prepare v4.1.14 release (#19037)Update all of nextjs to version 15.5.4Update tar 7.4.3 → 7.5.1 (minor) (#19035)Update @playwright/test 1.55.0 → 1.55.1 (patch) (#19033)Ensure first class inside className in React is migrated (#19031)Show version mismatch when running upgrade tool (#19028)Add `Upgrading from Tailwind CSS v…` when running upgrade tool (#19026)Update jiti 2.5.1 → 2.6.0 (minor) (#19029)Update bun 1.2.20 → 1.2.22 (patch) (#19007)Update @tailwindcss/typography 0.5.16 → 0.5.19 (minor) (#19014)Update prettier-plugin-organize-imports 4.2.0 → 4.3.0 (minor) (#19013)Update magic-string to version 0.30.19Update all of nextjs to version 15.5.2Update dedent 1.6.0 → 1.7.0 (minor) (#19010)Update eslint 9.33.0 → 9.35.0 (minor) (#19009)Update @types/semver 7.7.0 → 7.7.1 (patch) (#19005)Update @types/react 19.1.9 → 19.1.13 (patch) (#19003)Update @vitejs/plugin-react 5.0.0 → 5.0.3 (patch) (#19006)Update @types/react-dom 19.1.7 → 19.1.9 (patch) (#19004)Update @types/bun 1.2.20 → 1.2.22 (patch) (#19002)Add Maud templating support (#18988)Ensure files with only `@theme` produce no output when built (#18979)Revert "Update all pnpm dependencies (2025-09-20) (#18971)"Update all pnpm dependencies (2025-09-20) (#18971)Bump napi toolchain to 3.3 (#18947)Detect classes in markdown inline directives (#18967)Add plugin option documentation to the postcss plugin readme (#18940)Re-throw errors from PostCSS nodes (#18373)Bump Prettier (#18960)Use `default` export condition for `@tailwindcss/vite` (#18948)Show Lightning CSS warnings when optimizing/minifying in production (#18918)Do not migrate `variant = 'outline'` during upgrades (#18922)Proposal: Allow overwriting static utilities that have a namespace (#18056)Do not generate `grid-column` when configuring `grid-column-start` or `grid-column-end` (#18907)Fix CLI watcher cleanup race (#18905)Add `@container-size` utility (#18901)Merge suggestions when using `@utility` (#18900)Handle `@variant` inside `@custom-variant` (#18885)Handle `'` syntax in ClojureScript when extracting classes (#18888)Prepare v4.1.13 release (#18868)Do not allow variants to end with `-` or `_` (#18872)Do not allow variants to start with `-` (#18867)Consider variants starting with `@-` to be invalid (e.g. `@-2xl:flex`) (#18869)update changelogAdd '.vercel' to ignored content directories (#18855)chore: remove redundant words (#18853)update test after prettier changerun prettierFix missing code block delimiters in comment blocks (#18837)🚨 [security] Update all of nextjs 15.4.4 → 15.4.7 (patch) (#18838)Drop exact duplicate declarations from output CSS within a style rule (#18809)Hide internal fields from completions in `matchUtilities` (#18820)Update magic-string 0.30.17 → 0.30.18 (minor) (#18821)Update @playwright/test 1.54.2 → 1.55.0 (minor) (#18823)Replace deprecated `clip` with `clip-path` in `sr-only` (#18769)Migrate `supports` theme keys (#18817)Migrate `data` theme keys (#18816)Migrate `aria` theme keys (#18815)Show suggestions for known `matchVariant` values (#18798)Discard `matchVariant` matches with unknown named values (#18799)Don't transition `visibility` when using `transition` (#18795)Update eslint 9.32.0 → 9.33.0 (minor) (#18779)Update @vitejs/plugin-react 4.7.0 → 5.0.0 (major) (#18738)Drop warning from browser build (#18732)Release Notes
2.6.1
2.6.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
chore(release): v2.6.1chore: remove unused codechore: update depsbuild: revert to `terser-webpack-plugin` (#407)fix(interop): only passthrough default if it is not a promise (#408)chore: update benchchore(release): v2.6.0perf: lazy load babel transform (#405)fix: always use native for `node:` specifiers (#392)fix(cjs-interop): handle function default exports (#396)build: migrate to rspack (#404)test: new bench scripttest: update deno and bun native test ignoreschore: update depschore(deps): update all non-major dependencies (#393)chore(deps): update actions/checkout action to v5 (#394)chore(deps): update actions/setup-node action to v5 (#399)Commits
See the full diff on Github. The new version differs by 4 commits:
chore: release v0.30.19chore: update depsfix: this.outro need to be mapped (#300)feat: `replace(All)` support replacement for functions when the first parameter is a string (#304)Commits
See the full diff on Github. The new version differs by 3 commits:
3.1.0clean up handling of missing brotli/zstd in old node versionsAdd support for zstdCommits
See the full diff on Github. The new version differs by 2 commits:
chore(release): 2.3.0feat(types): added `TypedHookMap` type (#195)Commits
See the full diff on Github. The new version differs by 21 commits:
7.5.1fix: consistent TOCTOU behavior in sync t.list7.5.0changelog 7.5feat: add initial zstd supportci: don't bother testing on node 18update workflows, tshy configs7.4.4Fix some typosdocs(changelog): add missing v7 breaking changedocs: clean up duplicate onwarn optionsupdate all depsminizlib@3.1.0doc: fix lowlevel tar.Parser typoremove yallist from parse, but NOT from packUse built-in mkdir instead of mkdirpformat readmelimit normalize-unicode cache sizeremove dirCache from mkdir, unpackremove extraneous 'for example'docs on how to use onWriteEntry🆕 @emnapi/core (added, 1.5.0)
🆕 @emnapi/wasi-threads (added, 1.1.0)
🆕 @napi-rs/wasm-runtime (added, 1.0.5)
🆕 @tybys/wasm-util (added, 0.10.1)
🗑️ mkdirp (removed)
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
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.