chore(deps): bump the frontend-runtime-major group across 1 directory with 4 updates

[dependabot]

Bumps the frontend-runtime-major group with 4 updates in the /frontend directory: react-dropzone, @testing-library/jest-dom, tailwindcss and typescript.

Updates react-dropzone from 14.3.8 to 19.1.1

Release notes

Sourced from react-dropzone's releases.

v19.1.1

19.1.1 (2026-07-19)

Bug Fixes

• ignore drops on the dropzone while the file dialog is open (closes #1455) (4599a84)

v19.1.0

19.1.0 (2026-07-19)

Features

• support async validator (ec2af85)

v19.0.2

19.0.2 (2026-07-18)

Bug Fixes

• detect dragged files via items kind when types omit Files (#1409) (c678d38)

v19.0.1

19.0.1 (2026-07-18)

Bug Fixes

• hide file input in-flow to prevent scroll jump (fixes #1413) (d1d290c)

v19.0.0

19.0.0 (2026-07-18)

• fix!: accept files up to the limit instead of rejecting the batch (696d47c), closes #1355 #1358

BREAKING CHANGES

• acceptedFiles/onDropAccepted now returns the in-limit files that were previously rejected wholesale.

v18.3.0

18.3.0 (2026-07-18)

Features

... (truncated)

Commits

• 4599a84 fix: ignore drops on the dropzone while the file dialog is open (closes #1455)
• ec2af85 feat: support async validator
• c678d38 fix: detect dragged files via items kind when types omit Files (#1409)
• fcded10 docs: warn that a button root needs type=button inside a form (closes #1292)
• 36e92bd docs: note Android photo-picker hides camera (closes #1417)
• d1d290c fix: hide file input in-flow to prevent scroll jump (fixes #1413)
• 696d47c fix!: accept files up to the limit instead of rejecting the batch
• 03f0f6e feat: add isDragUnknown state and skip validator during drag (closes #1408, c...
• 2b8dcfb fix: prevent browser opening files dropped on disabled/noDrag dropzone (fixes...
• 5d14000 docs: add file dialog caveats for <label> root and open() timing
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-dropzone since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

Updates @testing-library/jest-dom from 6.9.1 to 7.0.0

Release notes

Sourced from @​testing-library/jest-dom's releases.

v7.0.0

7.0.0 (2026-07-20)

Features

• add toContainAnyBy* and toContainOneBy* query matchers (1e39089)

BREAKING CHANGES

• @​testing-library/dom is now a required peer dependency. The minimum supported Node.js version is now 22.

Repaired release for testing-library/jest-dom#731

v6.10.0

6.10.0 (2026-07-20)

Features

• add toContainAnyBy* and toContainOneBy* query matchers (#731) (cae44df)

Commits

• 1e39089 feat: add toContainAnyBy* and toContainOneBy* query matchers
• cae44df feat: add toContainAnyBy* and toContainOneBy* query matchers (#731)
• 55c07ce ci: switch release to npm trusted publishing (#726)
• 213256f docs: move toHaveSelection from the deprecated section (#717)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​testing-library/jest-dom since your current version.

Updates tailwindcss from 3.4.18 to 4.3.3

Release notes

Sourced from tailwindcss's releases.

v4.3.3

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)

v4.3.2

Fixed

• Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#20229)
• Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#20242)
• Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#20245)
• Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#20246)
• Allow @variant rules used in addBase(…) to use custom variants defined later (#20247)
• Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#20259)
• Generate font-size instead of color declarations for text-[--spacing(…)] (#20260)
• Prevent @source patterns from scanning unrelated sibling files and folders (#20263)
• Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#20269)
• Extract class candidates from conditional Maud syntax like p.text-black[condition] (#20269)
• Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#20277)
• Support class suggestions for named opacity modifiers from --opacity theme values (#20287)
• Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#20289)

v4.3.1

Added

• Add --silent option to suppress output in @tailwindcss/cli (#20100)

Fixed

• Remove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+ (#20028)
• Canonicalization: don't crash when plugin utilities throw for unsupported values (#20052)
• Allow @apply to be used with CSS mixins (#19427)
• Ensure not-* correctly negates @container queries, including style(…) queries (#20059)
• Ensure drop-shadow-* color utilities work with custom shadow values containing calc(…) (#20080)
• Fix 'Sourcemap is likely to be incorrect' warnings when using @tailwindcss/vite (#20103)
• Ensure @tailwindcss/webpack can be installed in Rspack projects without requiring webpack as a peer dependency (#20027)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.3.3] - 2026-07-16

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)

[4.3.2] - 2026-06-26

Fixed

• Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#20229)
• Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#20242)
• Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#20245)
• Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#20246)
• Allow @variant rules used in addBase(…) to use custom variants defined later (#20247)
• Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#20259)
• Generate font-size instead of color declarations for text-[--spacing(…)] (#20260)
• Prevent @source patterns from scanning unrelated sibling files and folders (#20263)
• Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#20269)
• Extract class candidates from conditional Maud syntax like p.text-black[condition] (#20269)
• Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#20277)
• Support class suggestions for named opacity modifiers from --opacity theme values (#20287)
• Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#20289)

[4.3.1] - 2026-06-12

Added

• Add --silent option to suppress output in @tailwindcss/cli (#20100)

Fixed

• Remove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+ (#20028)
• Canonicalization: don't crash when plugin utilities throw for unsupported values (#20052)
• Allow @apply to be used with CSS mixins (#19427)
• Ensure not-* correctly negates @container queries, including style(…) queries (#20059)

... (truncated)

Commits

• c2b24dd 4.3.3 (#20334)
• e48c5e8 Fix weird character rendering on Windows with Japanese locale (#20318)
• 35a3e9c Always produce \<length> value when optimizing --spacing(0) (#20319)
• 4af47fb Fix hues in achromatic theme colors to be none (#20314)
• 5835691 Handle CSS nesting natively (#20124)
• 67c745e Fix bug in attribute selector parsing (#20303)
• 2683903 Support fractional opacity modifiers for named shadow sizes (#20302)
• 04588b1 Fix theme() in JS plugins returning unresolved object instead of DEFAULT valu...
• b53fa09 fix: exclude iframes from focus-visible auto outline in Preflight (#20292)
• ef79119 Bump dependencies (#20300)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tailwindcss since your current version.

Updates typescript from 5.9.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

TypeScript 6.0

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

[github-actions]

PR Context Summary

• Linked issue(s): none
• Referenced but not closing: #1455, #1409, #1413, #1355, #1358, #1292, #1417, #1408, #731, #726, #717, #20297, #20298, #20292, #20299, #20302, #20303, #20310, #20124, #20314, #20319, #20325, #20318, #20329, #20335, #20336, #20229, #20242, #20245, #20246, #20247, #20259, #20260, #20263, #20269, #20277, #20287, #20289, #20100, #20028, #20052, #19427, #20059, #20080, #20103, #20027, #20334, #20300
• PR author trusted by GitHub: no
• Dependabot PR: yes
• PR assignee synced from linked issue: no change
• Macroscope review status: Waiting for under-review or ready-to-merge before triggering Macroscope.

Suggested issue links

• No strong issue match found yet.

Use Fixes #123 or Closes #123 in the PR body when one of the suggestions is the intended issue.
Manual rerun: Actions > PR Context Triage > Run workflow > set pr_number and force_review=true.

[Abhash-Chakraborty]

Not merging as-is — this is a Tailwind 3 -> 4 major and needs a real migration, not a version bump. frontend-check fails on a PostCSS error because v4 moves the plugin to @tailwindcss/postcss and swaps the config format for CSS-first @theme. react-dropzone 14 -> 19 and testing-library 6 -> 7 are also breaking on top of that.

I would rather split these: the low-risk ones can go on their own, and Tailwind v4 gets a dedicated PR where we can actually review the config migration and diff the rendered UI. Grouping four majors together means one bad one blocks all of them.

[macroscopeapp]

Approvability

Verdict: Needs human review

Unable to check for correctness in a2c8b6b. Major version bumps (TypeScript 5→7, Tailwind 3→4, react-dropzone 14→19) with breaking API changes that required configuration rewrites. The designated code owner should verify build and runtime behavior after these significant dependency upgrades.

No code changes detected at 1c4e083. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[Abhash-Chakraborty]

Pushed a migration commit — all four majors needed real changes, and frontend-check is green now (biome clean, 300 unit tests, build across all 21 routes, 14 Playwright e2e).

What it took: @tailwindcss/postcss replaces the v3 plugin and autoprefixer drops out; globals.css moves to @import "tailwindcss" with @config keeping tailwind.config.js authoritative, so no CSS-first @theme rewrite; tailwindcss-animate is v3-only so tw-animate-css replaces it (nothing in src/ uses those utilities today). react-dropzone 19 and jest-dom 7 needed no source changes.

Two things worth a second opinion before this merges. TypeScript 7 is the native rewrite and no longer exposes the JS compiler API Next links against, so next build cannot load it — I enabled experimental.useTypeScriptCli, which is Next 16.2 documented path, but it is an experimental flag in our production build config. And v4 changes how the app looks. Tailwind v3 silently emitted nothing for opacity modifiers on arbitrary var() colours, so 18 selectors like bg-[color:var(--void)]/92 were dead classes; v4 resolves them via color-mix() so they now actually render. Diffing v3 vs v4 builds of the same routes: ~6% of pixels move, max channel delta 39/765 — mostly the app header and a few panel backdrops picking up the tint the markup always asked for. Subtle and arguably a fix, but it is a global change to the shell.

[Abhash-Chakraborty]

Migration verified end to end: biome clean, 300 unit tests, production build across all 21 routes, 14 Playwright e2e including the dark-mode contrast checks. Compared the v3 and v4 CSS class inventories too — 2174 vs 2203 selectors, nothing lost (the only v3-only entry was the unused container utility; this app uses its own container-shell). Accepting the header/backdrop tint change as the fix it is, and the experimental TS-CLI flag as the documented path for TS 7.

[Abhash-Chakraborty]

Migration verified end to end: biome clean, 300 unit tests, production build across all 21 routes, 14 Playwright e2e including the dark-mode contrast checks. Compared the v3 and v4 CSS class inventories too — 2174 vs 2203 selectors, nothing lost (the only v3-only entry was the unused container utility; this app uses its own container-shell). Accepting the header/backdrop tint change as the fix it is, and the experimental TS-CLI flag as the documented path for TS 7.