Repository navigation
chore(deps): update tailwindcss monorepo to v4.3.5 - #1009
Conversation
7e9e83a
ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blockedHive flagged this PR (author @mergeraptor[bot], head
Hive did not add the |
8bdef13 to
b0a108a
Compare
b0a108a to
b369401
Compare
b369401 to
d42d14b
Compare
d42d14b to
4687a7c
Compare
There was a problem hiding this comment.
Summary: This automated update moves the website's styling toolkit (Tailwind CSS) from version 4.3.2 to 4.3.5. Only half of the update was made: the list of wanted versions changed, but the companion file that pins the exact versions to install did not. Because of that, the website's automated build and tests cannot install anything and fail before they run, so this cannot merge as it is.
What I need from you: Get the update bot to regenerate the version-pin file (re-run it, or check why its file update failed), then re-check CI.
correctness
- Lockfile not updated, so CI cannot install dependencies (in-scope, high). The PR changes only
package.json:52(@tailwindcss/vite4.3.2 → 4.3.5) andpackage.json:64(tailwindcss4.3.2 → 4.3.5).package-lock.jsonat this head still records"@tailwindcss/vite": "4.3.2"(line 32),"tailwindcss": "4.3.2"(line 44) andnode_modules/@tailwindcss/vite"version": "4.3.2"(lines 3673–3674). On head 4687a7c, both thetestjob (133391275809) and thewolves-movie-flowjob (133391276082) fail atnpm ciwithEUSAGE: "lock file's @tailwindcss/vite@4.3.2 does not satisfy @tailwindcss/vite@4.3.5". The same error is reported fortailwindcss,@tailwindcss/node,@tailwindcss/oxide,enhanced-resolve,lightningcssand the missingmagic-string@1.4.5. The bot's ownrenovate/artifactscheck reports "Artifact file update failure", which tells us its lockfile regeneration failed. No tests ran, so this head is not verified at all.
Fix: the bot regenerates this branch on its own schedule, so the fix has to come from the bot. Re-run it, or look at its artifact log to see whynpm installfailed. Hand-editing the branch would be overwritten. If the bot keeps failing, a maintainer can land the bump onmainwithnpm install -D @tailwindcss/vite@4.3.5 tailwindcss@4.3.5and commit both files together.
I could not check whether 4.3.5 changes any rendered styles, because no build ran on this head.
No findings from: security, intent-alignment, style, docs-currency.
Confidence: 3/5 (needs attention) — 1 high finding
— hive: agent=reviewer-2 backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325
|
Not approving yet. The bump itself is fine, but Renovate couldn't regenerate The cause is Renovate's npm, not Tailwind. Renovate ran npm 12, which refuses the @tailwindcss/oxide-wasm32-wasi 4.3.5 tarball (EALLOWREMOTE), while our CI uses npm 11. testsuite hit exactly this and fixed it by pinning Renovate's npm in projectbluefin/testsuite#1255. After that, its Tailwind 4.3.5 bump merged cleanly (projectbluefin/testsuite#1256). Fix for website: add |
|
The fix on main is tracked in #1031. |
4687a7c to
3815464
Compare
There was a problem hiding this comment.
Summary: This automated update moves the website's styling toolkit (Tailwind CSS) from version 4.3.2 to 4.3.5. The update is still incomplete. It changes the list of wanted versions but not the file that records the exact versions to install. Because of this, the site's automatic build and tests stop at the install step and cannot run.
What I need from you: Regenerate the lock file (npm install) on this branch, or let the update bot's next run do it, before merging.
This is a re-review at head 3815464. The previous head was 4687a7c.
- The previous finding is still present:
package-lock.jsonwas not updated (details below). - Most of the delta since the last review comes from a rebase onto
main(the GitHub compare reportsdiverged). That delta touches five workflow files,renovate.json,package.jsonandpackage-lock.json. The PR's own diff againstmainis still only the two version bumps inpackage.json:52andpackage.json:64. The workflow andrenovate.jsonchanges are not part of this PR.
correctness
package.json:52andpackage.json:64pin@tailwindcss/viteandtailwindcssto4.3.5. At this head,package-lock.jsonstill records4.3.2:- root entries at
package-lock.json:32and:44 node_modules/@tailwindcss/viteat:3674node_modules/tailwindcssat:9366
- root entries at
- CI at this head fails in the
npm cistep (.github/workflows/ci.yml:26) for both thetestjob (134136688792) and thewolves-movie-flowjob (134136689329). Log from thetestjob:
npm error Invalid: lock file's @tailwindcss/vite@4.3.2 does not satisfy @tailwindcss/vite@4.3.5
(The same error appears fortailwindcss,@tailwindcss/nodeand@tailwindcss/oxide.)
Lint, typecheck, tests and build are all skipped, so nothing verifies the upgrade itself. - Fix: run
npm installand commit the regeneratedpackage-lock.jsonto this branch. That is lock maintenance on the bot's branch, not a fix tomain. Alternatively, have Renovate/mergeraptor regenerate the lock file; check its lock-file maintenance and post-upgrade settings inrenovate.json.
No findings from: security, intent-alignment, style, docs-currency.
Confidence: 3/5 (needs attention) — 1 high finding
— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325
| "happy-dom": "21.0.4", | ||
| "playwright": "1.65.0", | ||
| "tailwindcss": "4.3.2", | ||
| "tailwindcss": "4.3.5", |
There was a problem hiding this comment.
package-lock.json still pins tailwindcss and @tailwindcss/vite at 4.3.2 (lines 32, 44, 3674 and 9366). Because of this, npm ci fails at this head with lock file's @tailwindcss/vite@4.3.2 does not satisfy @tailwindcss/vite@4.3.5. Run npm install and commit the regenerated lock file.
95564d5 to
18a32fd
Compare
There was a problem hiding this comment.
Summary: This automated update is supposed to move the website's styling toolkit (Tailwind) from version 4.3.2 to 4.3.5. The new commit changes the list of wanted versions, but it does not update the companion file that records the exact versions to install. The two files disagree, so the site's automated install step fails before any build or test can run. Merging this as it is would break the build on the main branch.
What I need from you: Regenerate the lock file for this update, or let the update bot do it, before merging.
Delta re-review: commit 95564d5 to 18a32fd. The delta is a rebase onto main. The vue-tsc 3.1.3→3.3.14 change in the delta comes from main and is not part of this PR. Against main, the PR only changes package.json.
Previous finding: still present. The lock file still pins Tailwind 4.3.2, so npm ci fails.
correctness
package.json:52andpackage.json:64request4.3.5. At this head,package-lock.jsonstill recordspackages[""].devDependenciesastailwindcss: 4.3.2and@tailwindcss/vite: 4.3.2. It also resolvesnode_modules/tailwindcss,@tailwindcss/vite,@tailwindcss/nodeand every@tailwindcss/oxide-*package at4.3.2. The PR diff does not touchpackage-lock.jsonat all.- CI at this head: the
testjob (135309953486, head_sha18a32fd) fails innpm ciwith`npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. - Fix: run
npm installon this change and commit the regeneratedpackage-lock.json. The other option is to enable Renovate lock-file maintenance orpostUpgradeTasksso the bot's next run does this. Nobody pushes to this branch, so a maintainer has to apply the fix.
No findings from: security, intent-alignment, style, docs-currency.
Confidence: 3/5 (needs attention) — 1 high finding
-- hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.327
| "happy-dom": "21.0.4", | ||
| "playwright": "1.65.1", | ||
| "tailwindcss": "4.3.2", | ||
| "tailwindcss": "4.3.5", |
There was a problem hiding this comment.
package-lock.json at this head still pins tailwindcss and @tailwindcss/vite (and all @tailwindcss/oxide-*) at 4.3.2. The PR does not touch the lock file. Because of that, npm ci fails with EUSAGE: the test job 135309953486 fails at head 18a32fd. Fix: run npm install and commit the regenerated package-lock.json.
|
Summary: This proposed dependency update still fails before tests can start because its dependency files disagree. The existing incident already tracks the repair, so no retry or branch change was made. CI run 44449583195 fails Tracked in #1046, whose maintainer-directed plan identifies #1040 for lockfile generation. Deferring to that existing work rather than duplicating it. 🐝 Hive Agent: -- hive: agent=ci-maintainer backend=copilot model=gpt-6.1-sol copilot=1.0.88 |
18a32fd to
45288bc
Compare
There was a problem hiding this comment.
Summary: This automated update raises the website's styling toolkit (Tailwind) from version 4.3.2 to 4.3.5. It still cannot merge: only the list of wanted versions was changed, not the companion file that records exactly what gets installed, so the build server refuses to install anything and every check fails. The problem flagged in the previous review is still present.
What I need from you: Regenerate the lock file for this update (or let the update bot retry), then re-run checks.
Re-review at head 45288bc3. Changes since last review (18a32fd2) are only the base-branch bumps carried in by the rebase (wrangler 4.163.0, workerd/miniflare 1.20261116.x, marked 18.2.1). Those are not part of this PR's diff and add no new findings.
Previous finding - lock file still pins Tailwind 4.3.2: still present (see inline thread on package.json:64).
package-lock.json:32,:44,:3690,:9309at this head still say4.3.2.testjob 135985226204 (head45288bc3) fails atnpm ci:Invalid: lock file's tailwindcss@4.3.2 does not satisfy tailwindcss@4.3.5.- Renovate's own
renovate/artifactscheck reports "Artifact file update failure", so the bot did not regenerate the lock file.
Fix on the bot side: tick the rebase/retry box so Renovate regenerates the lock file. A maintainer can also run npm install @tailwindcss/vite@4.3.5 tailwindcss@4.3.5 --save-exact on a branch and commit package-lock.json. Renovate overwrites any push to this branch, so the retry route is the cleaner one.
No findings from: security, intent-alignment, style, docs-currency.
Confidence: 3/5 (needs attention) — 1 high finding
-- hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.327
| "happy-dom": "21.0.4", | ||
| "playwright": "1.65.1", | ||
| "tailwindcss": "4.3.2", | ||
| "tailwindcss": "4.3.5", |
There was a problem hiding this comment.
correctness - package.json now asks for tailwindcss/@tailwindcss/vite 4.3.5, but package-lock.json at this head still pins 4.3.2 (lines 32, 44, 3690, 9309). npm ci in the test job (head 45288bc) fails: Invalid: lock file's tailwindcss@4.3.2 does not satisfy tailwindcss@4.3.5. renovate/artifacts reports "Artifact file update failure". Fix: retry Renovate so it regenerates the lock, or run npm install @tailwindcss/vite@4.3.5 tailwindcss@4.3.5 --save-exact and commit package-lock.json.
There was a problem hiding this comment.
Looks correct to me. Patch-level bump: tailwindcss and @tailwindcss/vite move together 4.3.2 to 4.3.5 in package.json and package-lock.json, so the plugin and core stay in lockstep. test and wolves-movie-flow are green on this head.
Heads-up for ordering: #1038 also regenerates package-lock.json. Whichever lands second will need a lockfile rebase (Renovate does this automatically for this PR).
Confidence: 5/5 (safe)
-- hive: agent=reviewer-2 backend=claude model=claude-opus-5-5 effort=medium claude=2.1.327
castrojo
left a comment
There was a problem hiding this comment.
LGTM! Tailwind v4.3.5 patch update with lockfile verified.
Assisted-by: Gemini via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: castrojo <castrojo@users.noreply.github.com>
castrojo
left a comment
There was a problem hiding this comment.
LGTM! Tailwind v4.3.5 and @tailwindcss/vite 4.3.5 with lockfile rebased onto latest main.
This PR contains the following updates:
4.3.2→4.3.54.3.2→4.3.5Release Notes
tailwindlabs/tailwindcss (@tailwindcss/vite)
v4.3.5Compare Source
Fixed
matchVariantplugin with thousands of values) (#20663)color-mix(…)without a color interpolation method (e.g.color-mix(var(--color-red-500))orcolor-mix(currentcolor 50%, transparent)) (#20658, #20666)@tailwindcss/oxide-wasm32-wasiloads instead of hanging forever (e.g. withNAPI_RS_FORCE_WASI=erroror in WebContainers) (#20667)as: '*.css'from the@tailwindcss/turbopacksetup in its README, because it breaks CSS modules (#20660)<!--and-->between top-level rules in CSS instead of throwing or swallowing the next rule (e.g.a { color: red } --> b { color: blue }) (#20665)@tailwindcss/oxide-wasm32-wasidetects changed and new source files after the first scan (e.g. in WebContainers) (#20487)skipLibCheck: falsecaused by imports of unshipped modules in the@tailwindcss/nodetype declarations (#20632)v4.3.4Compare Source
Added
@tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#20367)Fixed
@sourcefiles whose real paths aren't otherwise scanned (#20356)@scopewrap generated utilities instead of nesting inside them (#20369)@scoperules preserve their scoping semantics when flattened (#20369)@scopeby wrapping them in:where(:scope)(#20369)var()fallbacks (e.g.var(--tw-blur,)→var(--tw-blur, )) (#20373)max-[64rem]:flex→max-lg:flex) (#20380)@tailwindcss/vitefrom crashing on every edit under Vite's experimentalbundledDevmode (#20379)@tailwindcss/oxidefalls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasinow installs on all platforms, but only loads when no native binding is available) (#20383)%wand%Wliterals using angle brackets or custom delimiters (e.g.%w<flex>,%w|flex|), including in Slim and Haml templates (#20387)--default(…)values in functional@utilitydefinitions (e.g.--default(box alphabetic)no longer becomesboxalphabetic) (#20392).gitignorefiles (e.g./*followed by!/…patterns) (#20397)theme('…')namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of itsDEFAULTkey (#20399)@tailwindcss/vitefrom forcing full-page reloads for scanned files that Vite does not handle as modules (e.g..phpfiles) (#20414)unset(#20417)rounded-sm/[5],shadow-sm/foo,stroke-2/50) (#20419)and,or, andnotinside selectors insupports-[…]variants (e.g.supports-[selector(a:not(.foo))]:flex) (#20420)::ng-deepand:host-context()when optimizing CSS (#20434)bg-red-500/50/andgroup-hover/foo//bar:flex) (#20466)min-*,max-*, and container query variants with decimal values are sorted numerically (e.g.min-[40.25rem]beforemin-[40.5rem]) (#20512)\*/are closed correctly instead of swallowing the CSS that follows (e.g./* C:\temp\*/) (#20508)group-*andpeer-*variants (#20513)loadModuleandloadStylesheetcallbacks after compilation (#20531)&when moving a pseudo-element into*or**(e.g.[&_::before]:flex→**:[&::before]:flex) (#20550)Set.prototype.intersectionpolyfill incanonicalizeCandidates(…)returns the intersection instead of the first set on Node.js < 22 (#20562)theme(…)alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g.theme(colors.red.500/.12345)→text-red-500/[12.345%], nottext-red-500/[12.345]) (#20563)theme(…)alphas as an arbitrary percentage when a custom--opacity-*theme value would change the opacity (e.g.theme(colors.red.500/50%)→text-red-500/[50%]with--opacity-50: 10%) (#20563)@propertyfallback isn't applied in Safari versions that no longer supportmargin-trim: inline(#20569)dvminandsviand font-relative units likecapandrexas lengths in arbitrary values (e.g.text-[10dvmin]generatesfont-sizeinstead ofcolor) (#20516)tailwindcss canonicalizeso they don't end up in the results on stdout (#20561)input(pattern=/"/.source)) (#20547, #20572)--value(…)warnings (#20554)text-foreground text-primary→text-primary, nottext-card-checked-border) (#20540)mt-card mb-card→my-card, notmy-4) (#20574)@tailwindcss/postcssrewrites relativeurl(…)s of stylesheets that are inlined before it runs (e.g.@imports in Vite) in optimized builds (#20576)selection:*on a utility with a nested& > *rule) (#20575)w-[calc(1px]or[--x:a[b]) (#20577)collapse: truefrom taking exponentially longer when classes are linked through a utility that sets many properties (e.g.sr-only) (#20558)&is substituted inside:-moz-any(…)and:-webkit-any(…)in custom variants (e.g.@custom-variant firefox (:-moz-any(&));) (#20486)@tailwindcss/turbopackand@tailwindcss/webpackrebuild when the input CSS changes (e.g.next devwith Turbopack no longer serves the CSS of the previous edit) (#20582)--tw-*variable when an unrelated property has the same value (e.g.link mt-4no longer becomesmt-4whenlinksetsmargin-top: 16pxand--tw-translate-x: 16px) (#20593)@utilitynames as the CSS spec does (e.g.@theme { --color-\0: red; }no longer registers--color-0) (#20591)!importantinside strings, comments orurl()in declaration values as the important flag (e.g.content: "a !important b") (#20627);(e.g.--foo: baras the last declaration) (#20653);at the end of the CSS input (e.g.color: red) (#20655)v4.3.3Compare Source
Fixed
--watch --poll[=ms]in@tailwindcss/cliwhen filesystem events are unreliable or unavailable (#20297)bg-[#fff]andbg-[#FFF]→bg-white) (#20298)iframe:focus-visibleoutline styles (#20292)theme('colors.foo')in JS plugins resolves correctly when both--color-fooand--color-foo-barexist (#20299)shadow-sm/12.5,text-shadow-sm/12.5,drop-shadow-sm/12.5, andinset-shadow-sm/12.5(#20302)[data-foo]divas two selectors instead of one (#20303)@tailwindcss/postcssrebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)@tailwindcss/browserand Tailwind Play (#20124)oklch(#20314)--spacing(0)is optimized to0pxinstead of0so it remains a<length>when used incalc(…)(#20319)@parcel/watcheronly when needed in@tailwindcss/cli --watchmode, so one-off builds and--watch --pollwork when@parcel/watchercan't be loaded (#20325)system-uiandui-sans-serifso CJK text respects the page'slangattribute on Windows (#20318)@tailwindcss/upgradefrom rewriting ignored files when run from a subdirectory (#20329)@sourcerules pointing to nested files are scanned when later@sourcerules point to files in parent folders (#20335)@tailwindcss/vitefrom triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.