Repository navigation
chore(deps): pin dependencies - #881
renovate[bot] wants to merge 1 commit into
Conversation
|
Code ReviewRisk: Low — The dependency updates are scoped to Pins previously ranged dependencies and updates several development dependencies, including Shiki, Tailwind, Vite, Playwright, tsdown, and VitePress. The related Tailwind and Vitest package versions remain aligned. Still open from earlier reviews (6 findings):
Review usage: 5,504 in / 282 out tokens — $0.0017 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit 8aefaee. Previous review runsPrevious run archived 2026-11-14T07:54:46ZCode ReviewRisk: Low — The dependency changes are isolated to development tooling and do not introduce an evident runtime or data-integrity defect. Pins several previously ranged dependencies and updates multiple development tools to newer versions in Still open from earlier reviews (6 findings):
Review usage: 5,506 in / 208 out tokens — $0.0016 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit 7f4f796. Previous run archived 2026-11-13T19:38:50ZCode ReviewRisk: Medium — issues that should be addressed before merge. This change pins and updates the js-toolkit workspace dependencies. The corresponding root lockfile was not updated to reflect the new dependency specifications and versions. 1 issue found:
Still open from earlier reviews (5 findings):
Review usage: 41,002 in (27,879 cached) / 1,130 out tokens — $0.0052 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit 942d162. Previous run archived 2026-11-12T11:48:13ZCode ReviewRisk: High — blocking issues remain — resolve them before merge. This change pins several existing development dependencies and upgrades others, including the Vite, VitePress, Tailwind, SWC, and browser-testing toolchains. The corresponding 1 issue found:
Still open from earlier reviews (4 findings):
Review usage: 39,393 in (26,854 cached) / 876 out tokens — $0.0047 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit b28ebdb. Previous run archived 2026-11-09T17:44:56ZCode ReviewRisk: Low — The dependency version changes are safe to merge; no concrete defects are evident in the reviewed diff. Pins previously ranged dependencies and updates several development dependencies to newer fixed versions. The changes are limited to Still open from earlier reviews (4 findings):
Review usage: 5,508 in (3,066 cached) / 274 out tokens — $0.0010 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit ef1ce88. Previous run archived 2026-11-09T00:41:51ZCode ReviewRisk: Low — no blocking issues; safe to merge aside from nits. This change pins previously ranged development dependencies and updates several tooling packages to newer exact versions. The browser-specific Vitest packages are moved to 4.1.12 while Still open from earlier reviews (4 findings):
Review usage: 15,803 in (8,574 cached) / 814 out tokens — $0.0030 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit d2e0fa3. Previous run archived 2026-11-09T00:39:14ZCode ReviewRisk: Medium — issues that should be addressed before merge. This MR pins existing dependencies and updates several development-tool versions in 1 issue found:
Still open from earlier reviews (3 findings):
Review usage: 53,665 in (40,236 cached) / 935 out tokens — $0.0053 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit e1c163b. Previous run archived 2026-11-08T14:14:29ZCode ReviewRisk: High — blocking issues remain — resolve them before merge. This change pins and upgrades the js-toolkit development dependencies in 1 issue found:
Still open from earlier reviews (2 findings):
Review usage: 39,050 in (27,189 cached) / 992 out tokens — $0.0047 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit df6a4ab. Previous run archived 2026-11-06T19:24:07ZCode ReviewRisk: Low — The dependency updates are version-pinned and should be safe to merge, with no demonstrable defects in the diff. This change replaces floating version ranges and updates several development dependencies to newer fixed versions. No application or runtime source code is modified. Still open from earlier reviews (2 findings):
Review usage: 5,507 in / 200 out tokens — $0.0016 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit 90110e9. Previous run archived 2026-11-06T00:58:02ZCode ReviewRisk: Low — The dependency changes are isolated to development tooling and pin the listed packages to exact versions; no blocking issues were found. Updates the js-toolkit development dependencies, including version upgrades for documentation, build, styling, and test tooling. The package manifest now uses exact versions for the affected dependencies. Still open from earlier reviews (2 findings):
Review usage: 11,625 in (5,505 cached) / 449 out tokens — $0.0022 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit b845ba0. Previous run archived 2026-11-05T11:13:19ZCode ReviewRisk: Low — The dependency pins and version updates are confined to development tooling, with no concrete runtime defect visible in the diff. Updates the js-toolkit development dependencies by pinning previously ranged versions and advancing several toolchain packages. No blocking or actionable issues were found. Still open from earlier reviews (2 findings):
Review usage: 5,508 in / 239 out tokens — $0.0017 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.11.1 for commit 91347f7. |
| "@rollup/plugin-swc": "^0.4.1", | ||
| "@shikijs/vitepress-twoslash": "4.0.2", | ||
| "@rollup/plugin-swc": "0.4.1", | ||
| "@shikijs/vitepress-twoslash": "4.5.0", |
There was a problem hiding this comment.
issue: Lockfile remains inconsistent with workspace manifest
The workspace entry in package-lock.json still records the previous dependency versions and ranges, including vite: "8.2.1", while this manifest now requires different values. npm ci validates this relationship and exits instead of installing dependencies; regenerate and commit the lockfile.
Confidence: high.
Reviewed by @weareikko/code-review v0.9.9 for commit 4ec4dc7.
03a1ef2 to
d1e5bc6
Compare
b0895f2 to
419cef6
Compare
| "@tailwindcss/vite": "4.2.2", | ||
| "@vitest/browser": "4.1.10", | ||
| "@vitest/browser-playwright": "4.1.10", | ||
| "@rollup/plugin-swc": "0.4.1", |
There was a problem hiding this comment.
issue: Update the lockfile with these dependency changes
The committed package-lock.json still records the old js-toolkit dependency ranges and versions, including @shikijs/vitepress-twoslash at 4.0.2, while this manifest requires 4.5.0 and other updated exact versions. Because the lockfile is stale, npm ci will reject the manifest/lockfile mismatch and clean installs will not use the pinned dependencies; regenerate and commit package-lock.json.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit 419cef6.
0c6e37c to
c9164c6
Compare
| "@tailwindcss/vite": "4.2.2", | ||
| "@vitest/browser": "4.1.10", | ||
| "@vitest/browser-playwright": "4.1.10", | ||
| "@rollup/plugin-swc": "0.4.1", |
There was a problem hiding this comment.
issue: Regenerate the lockfile for the updated dependency manifest
The workspace entry in package-lock.json still declares the previous versions and ranges, including @rollup/plugin-swc as ^0.4.1 and vite as 8.2.4, while this manifest changes them. npm ci validates the lockfile against workspace manifests and will reject this mismatch; regenerate package-lock.json and commit the resulting dependency resolutions.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit c9164c6.
90110e9 to
df6a4ab
Compare
| "@vitest/browser": "4.1.10", | ||
| "@vitest/browser-playwright": "4.1.10", | ||
| "@rollup/plugin-swc": "0.4.1", | ||
| "@shikijs/vitepress-twoslash": "4.6.0", |
There was a problem hiding this comment.
issue (blocking): Regenerate the lockfile for the dependency changes
The package manifest now requires @shikijs/vitepress-twoslash 4.6.0 and other changed versions, but package-lock.json still records the old packages/js-toolkit dependency specification, including 4.0.2. A clean npm ci detects this manifest-lockfile mismatch and fails before dependencies are installed. Regenerate and commit the root lockfile.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit df6a4ab.
df6a4ab to
e1c163b
Compare
| "@vitest/browser": "4.1.10", | ||
| "@vitest/browser-playwright": "4.1.10", | ||
| "@rollup/plugin-swc": "0.4.1", | ||
| "@shikijs/vitepress-twoslash": "4.6.0", |
There was a problem hiding this comment.
issue: Regenerate the lockfile for updated dependency pins
The workspace manifest now declares different dependency ranges and versions, but the committed root package-lock.json still records the old values, such as vite 8.2.4 and @tailwindcss/vite 4.2.2. npm's lockfile validation will reject this mismatch during npm ci, so regenerate and commit package-lock.json with these changes.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit e1c163b.
ef1ce88 to
b28ebdb
Compare
| "@vitest/browser": "4.1.10", | ||
| "@vitest/browser-playwright": "4.1.10", | ||
| "@rollup/plugin-swc": "0.4.1", | ||
| "@shikijs/vitepress-twoslash": "4.6.0", |
There was a problem hiding this comment.
issue (blocking): Regenerate the lockfile for changed dependencies
The committed package-lock.json still records the previous packages/js-toolkit dependency specifications, including vite 8.2.4, vitepress 2.0.0-alpha.19, and @vitest/browser 4.1.10, while this manifest requires different versions. npm ci validates workspace manifests against the lockfile and will reject this inconsistent tree instead of installing it. Run the package manager install/update and commit the resulting lockfile.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit b28ebdb.
b28ebdb to
942d162
Compare
| "@tailwindcss/vite": "4.2.2", | ||
| "@vitest/browser": "4.1.10", | ||
| "@vitest/browser-playwright": "4.1.10", | ||
| "@rollup/plugin-swc": "0.4.1", |
There was a problem hiding this comment.
issue: Regenerate the lockfile for updated workspace dependencies
The root package-lock.json still records the previous packages/js-toolkit dependency specifications, including @shikijs/vitepress-twoslash at 4.0.2 and vite at 8.2.4, while this manifest contains different specs and versions. npm ci validates workspace manifests against the lockfile and will reject this repository until package-lock.json is regenerated and committed.
Confidence: high.
Reviewed by @weareikko/code-review v0.11.1 for commit 942d162.
7f4f796 to
43f247b
Compare
8aefaee to
093e8d9
Compare
|
Renovate review (high risk: Checks: CI on head Needed: group |
093e8d9 to
a516e82
Compare
a516e82 to
5ef9e75
Compare
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^0.4.1→0.4.14.0.2→4.6.03.0.0→3.0.13.0.2^1.15.47→1.16.224.2.2→4.3.54.1.10→4.1.124.1.10→4.1.12^7.8.0→7.8.0^1.50.0→1.65.14.2.2→4.3.50.22.14→0.23.78.2.4→8.3.82.0.0-alpha.19→2.0.0-alpha.211.12.0→1.15.0Add the preset
:preserveSemverRangesto your config if you don't want to pin your dependencies.Release Notes
shikijs/shiki (@shikijs/vitepress-twoslash)
v4.6.0Compare Source
🐞 Bug Fixes
ShikiStreamTokenizeroffsets and CRLF handling withcodeToTokens- by @xyrolle in #1335 (f8aba)🏎 Performance
View changes on GitHub
v4.5.0Compare Source
🚀 Features
🐞 Bug Fixes
#and--comments in rose-pine theme - by @anandghegde in #1317 (63e6d)🏎 Performance
View changes on GitHub
v4.4.3Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v4.4.2Compare Source
🐞 Bug Fixes
🏎 Performance
View changes on GitHub
v4.4.1Compare Source
🚀 Features
View changes on GitHub
v4.4.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v4.3.1Compare Source
🚀 Features
typefield forThemedToken- by @ije in #1293 (585b5)View changes on GitHub
v4.3.0Compare Source
🚀 Features
View changes on GitHub
v4.2.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v4.1.0Compare Source
🐞 Bug Fixes
tsModuletocreateTwoslasher- by @arthurfiorette in #1271 (be89a)View changes on GitHub
studiometa/tailwind-config (@studiometa/tailwind-config)
v3.0.1Compare Source
Changed
## [Unreleased]section with.changelog/fragments checked on pull requests byweareikko/changelog, and release from thepublish-and-releaseworkflow, which bumps the version, folds the fragments intoCHANGELOG.md, tags, publishes to npm and creates the GitHub release (#137)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)v4.3.2Compare Source
Fixed
auto-rows-*andauto-cols-*utilities (e.g.auto-rows-12andauto-cols-16) (#20229)@tailwindcss/cliin--watchmode from crashing on Windows when@sourcepoints to a directory that doesn't exist (#20242)@tailwindcss/vitefrom crashing in Deno v2.8.x whencontext.parentURLis not a valid URL (#20245)@tailwindcss/cliin--watchmode rebuilds when the input CSS file changes in an ignored directory (#20246)@variantrules used inaddBase(…)to use custom variants defined later (#20247)@tailwindcss/vitefrom crashing during HMR when scanned files or directories are deleted (#20259)font-sizeinstead ofcolordeclarations fortext-[--spacing(…)](#20260)@sourcepatterns from scanning unrelated sibling files and folders (#20263)%]…[%in.tt,.tt2, and.txfiles (#20269)p.text-black[condition](#20269)@position-tryrules from triggering unknown at-rule warnings when optimizing CSS (#20277)--opacitytheme values (#20287)@tailwindcss/postcsswhen used with newer PostCSS patch releases (#20289)v4.3.1Compare Source
Added
--silentoption to suppress output in@tailwindcss/cli(#20100)Fixed
Module#registerHooksinstead ofModule#registeron Node 26+ (#20028)@applyto be used with CSS mixins (#19427)not-*correctly negates@containerqueries, includingstyle(…)queries (#20059)drop-shadow-*color utilities work with custom shadow values containingcalc(…)(#20080)@tailwindcss/vite(#20103)@tailwindcss/webpackcan be installed in Rspack projects without requiringwebpackas a peer dependency (#20027)calc(…)expressions (e.g.px-[calc(1rem+0px)]→px-[calc(1rem+0)]) (#20127)left-[99999px]→left-[99999px], notleft-24999.75) (#20130)@tailwindcss/cliin--watchmode recovers when a tracked dependency is deleted and restored (#20137)@tailwindcss/clibinaries are ignored when scanning for class candidates (#20139)addClass(…)andremoveClass(…)calls (#20198)@variantto be used insideaddBase(#19480)@sourceglobs with symlinks are preserved (#20203)@sourcerules can re-include files excluded by earlier@source notrules (#20203)@utilityrules (#20205)inset-shadow-noneand other inset shadows work correctly (#20208)@sourcedirectories are scanned even when ignored by git (#20214)@sourceglobs ending in**/*preserve dynamic path segments to avoid scanning too many files (#20217)calc(…)divisions when the result would require high precision (e.g.w-[calc(100%/3.5)]→w-[calc(100%/3.5)], notw-[28.571428571428573%]) (#20221)@tailwindcss/postcss(#20228)Changed
0instead ofcalc(var(--spacing) * 0)for spacing utilities likem-0andleft-0(#20196)var(--spacing)instead ofcalc(var(--spacing) * 1)for spacing utilities likem-1andleft-1(#20196)v4.3.0Compare Source
Added
@container-sizeutility (#18901)scrollbar-{auto,thin,none}utilities forscrollbar-width, andscrollbar-thumb-*/scrollbar-track-*color utilities forscrollbar-color(#19981, #20019)scrollbar-gutter-*utilities (#20018)zoom-*utilities (#20020)tab-*utilities (#20022)@variantwith stacked variants (e.g.@variant hover:focus { … }) (#19996)@variantwith compound variants (e.g.@variant hover, focus { … }) (#19996)--default(…)in--value(…)and--modifier(…)for functional@utilitydefinitions (#19989)Fixed
@pluginresolves package JavaScript entries instead of browser CSS entries when using@tailwindcss/vite(#19949)@importand@pluginpaths resolving from the wrong directory when using@tailwindcss/vite(#19965)@variantare processed by@tailwindcss/vite(#19966)basewhenresult.opts.fromis not provided when using@tailwindcss/postcss(#19980)_whitespace in arbitrary values (#19986)w-[calc(100%---spacing(60))]→w-[calc(100%-(--spacing(60)))]) (#19986)-mt-[20in]→mt-[-20in], notmt-[-1920px]) (#19988):has()variants from[&:has(…)]tohas-[…](#19991)styleattributes (e.g.style="flex-grow: 1"→style="flex-grow: 1", notstyle="grow: 1") (#19918)@utilitydefinitions with the same name but different value types (#19777)PluginWithConfigtype fromtailwindcss/pluginto fix errors when inferring plugin config types (#19707)startandendlegacy utilities without values do not generate CSS (#20003)--value(…)is required in functional@utilitydefinitions (#20005)-left-[(var(--a)+var(--b))]) (#20011)v4.2.4Compare Source
Fixed
@importand@pluginstill resolve correctly when using Vite aliases in@tailwindcss/vite(#19947)v4.2.3Compare Source
Fixed
tracking-*utilities by preferring non-negative utilities (e.g.-tracking-tighter→tracking-wider) (#19827)Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.