[ChronosSF]

Summary

• Grids: igniteui-webcomponents-grids ^7.3.0 → ^7.4.0-beta.1 in the root, all 316 samples that use it, and scripts/update-ig.js.
• Theming: igniteui-theming → ^30.2.0. This bumps the root (from ^29.0.0) and the four samples that list it (from ^25.0.0). The new grids beta is built from igniteui-angular's latest beta, which already uses theming 30. igniteui-theming is now also in update-ig.js so the root and sample specs stay in sync.
• Audit fix (piggyback): npm audit fix, lockfile-only, with in-range bumps such as vite 8.3.7, rolldown 1.2.18, express 5.3.0, hono 4.13.17 and @modelcontextprotocol/sdk 1.32.2. The one advisory audit fix couldn't resolve, the nested zod@3.25.76 under igniteui-theming@29 (GHSA-mrhx-c7xc-m3w5, high), goes away with the theming bump. npm audit: 2 high → 0.

Theming 30: one sample needed a fix

Theming 30 changes palette()'s default shade generator to fitted, which recomputes every shade from the input colors. grids/grid-lite/styling-custom-theme calls palette() with custom colors. Under the new generator its --ig-primary-500 became rgb(115, 108, 10) instead of the given #ddd020, and the grid visibly changed: navy rows turned near-black, the filter buttons went from blue to grey, and the stars darkened. The sample now passes $generator: 'legacy' to palette(), which keeps its current look.

The other three samples need no changes:

• styling-config-themes and layouts/tailwind/styling use the preset palettes, whose values didn't change.
• inputs/button-group/tailwind-styling lists igniteui-theming but never imports it.

Verification

• Rendering: I screenshotted all four samples in the Astro dev server, covering all 8 themes of styling-config-themes (11 shots), with Playwright, seeded random data and a fixed clock. I compared theming 29.0.0 with the original SCSS (current vnext) against this branch: all 11 are pixel-identical. A repeat run matched exactly, and a control run on theming 30 without the legacy fix flagged ~87% of the styling-custom-theme pixels as different.
• Compiled CSS: across the four samples, no existing declaration changes or is removed. Theming 30 only adds new custom properties (--ig-*-seed, --ig-surface-{base,sunken,raised,overlay,container} and their contrasts), and neither igniteui-webcomponents 7.4.1 nor igniteui-grid-lite 0.11.0 reads them.
• npm audit reports 0 vulnerabilities.

Notes

• 7.4.0-beta.1 is a prerelease.
• Compared with the old ^25.0.0 spec, someone running styling-config-themes on its own will see slightly different Indigo preset shades. That change came with theming 29, which the sample browser already uses.

🤖 Generated with Claude Code