Skip to content

chore(deps): update tailwindcss monorepo to v4.3.5 - #1009

Merged
castrojo merged 1 commit into
mainfrom
renovate/tailwindcss-monorepo
Nov 20, 2026
Merged

castrojo merged 1 commit into
mainfrom
renovate/tailwindcss-monorepo

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@tailwindcss/vite (source) 4.3.2 → 4.3.5 age confidence
tailwindcss (source) 4.3.2 → 4.3.5 age confidence

Release Notes

tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.3.5

Compare Source

Fixed
  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#​20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#​20658, #​20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#​20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#​20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#​20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#​20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#​20632)

v4.3.4

Compare Source

Added
  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#​20367)
Fixed
  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#​20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#​20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#​20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#​20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#​20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#​20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#​20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#​20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#​20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#​20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#​20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#​20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#​20408)
  • Drop invalid UTF-8 candidates during class detection (#​20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#​20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#​20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#​20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#​20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#​20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#​20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#​20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#​20508)
  • Improve style invalidation performance of group-* and peer-* variants (#​20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#​20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#​20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#​20562)
  • Canonicalization: ensure inline 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%], not text-red-500/[12.345]) (#​20563)
  • Canonicalization: preserve inline 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)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#​20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#​20516)
  • Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#​20561)
  • Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#​20547, #​20572)
  • Underline the correct occurrence of an unsupported data type in --value(…) warnings (#​20554)
  • Canonicalization: prefer an existing candidate when collapsing utilities over another utility with the same default theme value (e.g. text-foreground text-primary → text-primary, not text-card-checked-border) (#​20540)
  • Canonicalization: don't collapse utilities into a utility that uses another theme variable with the same default value (e.g. mt-card mb-card → my-card, not my-4) (#​20574)
  • Ensure @tailwindcss/postcss rewrites relative url(…)s of stylesheets that are inlined before it runs (e.g. @imports in Vite) in optimized builds (#​20576)
  • Drop nested rules that put a combinator after a pseudo-element when using pseudo-element variants (e.g. selection:* on a utility with a nested & > * rule) (#​20575)
  • Don't generate CSS for arbitrary values with unbalanced parentheses or brackets (e.g. w-[calc(1px] or [--x:a[b]) (#​20577)
  • Canonicalization: prevent collapse: true from taking exponentially longer when classes are linked through a utility that sets many properties (e.g. sr-only) (#​20558)
  • Ensure & is substituted inside :-moz-any(…) and :-webkit-any(…) in custom variants (e.g. @custom-variant firefox (:-moz-any(&));) (#​20486)
  • Ensure the standalone macOS binaries have a valid code signature, so macOS 27 no longer kills them at launch (#​20578)
  • Ensure @tailwindcss/turbopack and @tailwindcss/webpack rebuild when the input CSS changes (e.g. next dev with Turbopack no longer serves the CSS of the previous edit) (#​20582)
  • Canonicalization: don't drop a utility that sets a --tw-* variable when an unrelated property has the same value (e.g. link mt-4 no longer becomes mt-4 when link sets margin-top: 16px and --tw-translate-x: 16px) (#​20593)
  • Decode single-digit hexadecimal escapes in theme variable and @utility names as the CSS spec does (e.g. @theme { --color-\0: red; } no longer registers --color-0) (#​20591)
  • Don't treat !important inside strings, comments or url() in declaration values as the important flag (e.g. content: "a !important b") (#​20627)
  • Parse a custom property at the end of the input when it has no trailing ; (e.g. --foo: bar as the last declaration) (#​20653)
  • Keep a declaration without a ; at the end of the CSS input (e.g. color: red) (#​20655)

v4.3.3

Compare Source

Fixed
  • Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#​20297)
  • Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#​20298)
  • Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#​20292)
  • Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#​20299)
  • Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#​20302)
  • Parse selectors like [data-foo]div as two selectors instead of one (#​20303)
  • Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#​20310)
  • Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#​20124)
  • Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#​20314)
  • Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#​20319)
  • Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#​20325)
  • Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#​20318)
  • Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#​20329)
  • Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#​20335)
  • Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#​20336)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Nov 15, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor
7e9e83a

ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blocked

Hive flagged this PR (author @mergeraptor[bot], head 7e9e83af6562) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 2 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • package-lock.json
    • package.json

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

@hivecommons-hive hivecommons-hive Bot added stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it and removed stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it labels Nov 15, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from 8bdef13 to b0a108a Compare November 15, 2026 21:07
@hivecommons-hive hivecommons-hive Bot added stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it and removed stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it labels Nov 15, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from b0a108a to b369401 Compare November 16, 2026 03:11
@hivecommons-hive hivecommons-hive Bot added stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it and removed stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it labels Nov 16, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from b369401 to d42d14b Compare November 16, 2026 09:12
@hivecommons-hive hivecommons-hive Bot added stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it and removed stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it labels Nov 16, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from d42d14b to 4687a7c Compare November 16, 2026 15:11
@hivecommons-hive hivecommons-hive Bot removed the stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it label Nov 16, 2026
@hivecommons-hive hivecommons-hive Bot added the stage/stalled No activity (head, comment, review, CI, label) longer than the stage expects; nobody is working it label Nov 16, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/vite 4.3.2 → 4.3.5) and package.json:64 (tailwindcss 4.3.2 → 4.3.5). package-lock.json at this head still records "@tailwindcss/vite": "4.3.2" (line 32), "tailwindcss": "4.3.2" (line 44) and node_modules/@tailwindcss/vite "version": "4.3.2" (lines 3673–3674). On head 4687a7c, both the test job (133391275809) and the wolves-movie-flow job (133391276082) fail at npm ci with EUSAGE: "lock file's @tailwindcss/vite@4.3.2 does not satisfy @tailwindcss/vite@4.3.5". The same error is reported for tailwindcss, @tailwindcss/node, @tailwindcss/oxide, enhanced-resolve, lightningcss and the missing magic-string@1.4.5. The bot's own renovate/artifacts check 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 why npm install failed. Hand-editing the branch would be overwritten. If the bot keeps failing, a maintainer can land the bump on main with npm install -D @tailwindcss/vite@4.3.5 tailwindcss@4.3.5 and 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

@Danathar

Copy link
Copy Markdown
Contributor

Not approving yet. The bump itself is fine, but Renovate couldn't regenerate package-lock.json, so npm ci fails ("lock file's @tailwindcss/vite@4.3.2 does not satisfy @tailwindcss/vite@4.3.5").

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 "constraints": { "npm": "^11.20.0" } to renovate.json on main, then tick the rebase checkbox here.

@Danathar

Copy link
Copy Markdown
Contributor

The fix on main is tracked in #1031.

@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from 4687a7c to 3815464 Compare November 17, 2026 15:09

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.json was not updated (details below).
  • Most of the delta since the last review comes from a rebase onto main (the GitHub compare reports diverged). That delta touches five workflow files, renovate.json, package.json and package-lock.json. The PR's own diff against main is still only the two version bumps in package.json:52 and package.json:64. The workflow and renovate.json changes are not part of this PR.

correctness

  • package.json:52 and package.json:64 pin @tailwindcss/vite and tailwindcss to 4.3.5. At this head, package-lock.json still records 4.3.2:
    • root entries at package-lock.json:32 and :44
    • node_modules/@tailwindcss/vite at :3674
    • node_modules/tailwindcss at :9366
  • CI at this head fails in the npm ci step (.github/workflows/ci.yml:26) for both the test job (134136688792) and the wolves-movie-flow job (134136689329). Log from the test job:
    npm error Invalid: lock file's @tailwindcss/vite@4.3.2 does not satisfy @tailwindcss/vite@4.3.5
    (The same error appears for tailwindcss, @tailwindcss/node and @tailwindcss/oxide.)
    Lint, typecheck, tests and build are all skipped, so nothing verifies the upgrade itself.
  • Fix: run npm install and commit the regenerated package-lock.json to this branch. That is lock maintenance on the bot's branch, not a fix to main. Alternatively, have Renovate/mergeraptor regenerate the lock file; check its lock-file maintenance and post-upgrade settings in renovate.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

Comment thread package.json
"happy-dom": "21.0.4",
"playwright": "1.65.0",
"tailwindcss": "4.3.2",
"tailwindcss": "4.3.5",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from 95564d5 to 18a32fd Compare November 19, 2026 03:10
@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed hive:unauthorized stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue labels Nov 19, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:52 and package.json:64 request 4.3.5. At this head, package-lock.json still records packages[""].devDependencies as tailwindcss: 4.3.2 and @tailwindcss/vite: 4.3.2. It also resolves node_modules/tailwindcss, @tailwindcss/vite, @tailwindcss/node and every @tailwindcss/oxide-* package at 4.3.2. The PR diff does not touch package-lock.json at all.
  • CI at this head: the test job (135309953486, head_sha 18a32fd) fails in npm ci with `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync.
  • Fix: run npm install on this change and commit the regenerated package-lock.json. The other option is to enable Renovate lock-file maintenance or postUpgradeTasks so 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

Comment thread package.json
"happy-dom": "21.0.4",
"playwright": "1.65.1",
"tailwindcss": "4.3.2",
"tailwindcss": "4.3.5",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@hivecommons-hive hivecommons-hive Bot added hive:unauthorized stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Nov 19, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

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 npm ci: the lockfile contains Tailwind 4.3.2 but the update requests 4.3.5. The mandatory baseline helper returns DEFER_TO_INCIDENT for test; main is green and three current sibling PRs fail that check.

Tracked in #1046, whose maintainer-directed plan identifies #1040 for lockfile generation. Deferring to that existing work rather than duplicating it.


🐝 Hive Agent: ci-maintainer | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: 6b266cc1ba6d0d7d6fed50459c80f5d6b3b4c602

-- hive: agent=ci-maintainer backend=copilot model=gpt-6.1-sol copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 19, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/tailwindcss-monorepo branch from 18a32fd to 45288bc Compare November 20, 2026 00:19
@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it hive:unauthorized and removed hive:unauthorized stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue labels Nov 20, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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, :9309 at this head still say 4.3.2.
  • test job 135985226204 (head 45288bc3) fails at npm ci: Invalid: lock file's tailwindcss@4.3.2 does not satisfy tailwindcss@4.3.5.
  • Renovate's own renovate/artifacts check 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

Comment thread package.json
"happy-dom": "21.0.4",
"playwright": "1.65.1",
"tailwindcss": "4.3.2",
"tailwindcss": "4.3.5",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
castrojo previously approved these changes Nov 20, 2026

@castrojo castrojo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 castrojo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Tailwind v4.3.5 and @tailwindcss/vite 4.3.5 with lockfile rebased onto latest main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants