Update @tailwindcss/postcss 4.1.18 → 4.2.1 (minor)#562
Update @tailwindcss/postcss 4.1.18 → 4.2.1 (minor)#562depfu[bot] wants to merge 1 commit intomainfrom
Conversation
|
The files' contents are under analysis for test generation. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
|
|
Overall Grade |
Security Reliability Complexity Hygiene Coverage |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| Test coverage | Mar 4, 2026 1:40p.m. | Review ↗ | |
| Secrets | Mar 4, 2026 1:40p.m. | Review ↗ | |
| JavaScript | Mar 4, 2026 1:40p.m. | Review ↗ |
Code Coverage Summary
| Language | Line Coverage (Overall) |
|---|---|
| Aggregate | 93.8% |
| Javascript | 93.8% |
➟ Additional coverage metrics may have been reported. See full coverage report ↗
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
@depfu merge |
|
@depfu recreate |
8446109 to
701ace7
Compare
|
Infisical secrets check: ✅ No secrets leaked! 💻 Scan logs2026-03-04T13:40:36Z INF scanning for exposed secrets...
1:40PM INF 470 commits scanned.
2026-03-04T13:40:36Z INF scan completed in 369ms
2026-03-04T13:40:36Z INF no leaks found
|
|



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.18 → 4.2.1)
Sorry, we couldn't find anything useful about this release.
Release Notes
1.8.1
1.8.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
1.8.1[Backport] feat: add support for Float16Array (#191)1.8.0[Backport] feat: add node_api_set_prototype (#189)Release Notes
1.8.1
1.8.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
1.8.1[Backport] feat: add support for Float16Array (#191)1.8.0[Backport] feat: add node_api_set_prototype (#189)Sorry, we couldn't find anything useful about this release.
Release Notes
5.20.0
5.19.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
chore(release): 5.20.0chore(deps): bump minimatch (#478)feat(tsconfig): enable trailing comma support for JSONC (#479)fix(tsconfig): support JSONC comments in tsconfig.json files (#476)fix(tsconfig): detect circular extends to prevent infinite loop (#477)test: add null-byte escape test cases for '#' handling (#473)feat(tsconfig): add baseUrl option to override tsconfig baseUrl (#472)chore(release): 5.19.0chore: update eslint config webpack (#471)feat: added TsconfigPathsPlugin (replacement for tsconfig-paths-webpack-plugin) (#463)chore: migrate to npm from yarn (#469)Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
Release Notes
1.31.0
Does any of this look wrong? Please let us know.
Sorry, we couldn't find anything useful about this release.
🗑️ tailwindcss (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