Dependency Upgrade — Astro 5 → 7
Cogs-site catches up with the rest of the Astro Knots fleet — Astro jumps two majors in one clean pass, Tailwind CSS patches to latest, and typecheck tooling gets added for the first time.
Why Care?
This entry from earlier the same day (2026-07-06_01.md) flagged "Upgrade from Astro 5 → 7" as the top item under What's Next. This entry closes that out — cogs-site now matches the rest of the Astro Knots fleet on its Astro major version, ahead of any new feature work.
What Changed
Safe updates (patch/minor) first:
| Package | From | To |
astro | 5.15.1 | 5.18.2 (intermediate, within the ^5 range) |
tailwindcss | 4.1.16 | 4.3.2 |
@tailwindcss/cli | 4.1.16 | 4.3.2 |
Verified with pnpm run build (runs pnpm run build:tailwind && astro build) — passed cleanly.
Major upgrade:
| Package | From | To |
astro | 5.18.2 | 7.0.6 |
Astro allows a direct major-version jump (5 → 7 in one pnpm add astro@latest), and this site's minimal config (astro.config.mjs had zero non-default options, no @astrojs/transitions imports, no inlineStylesheets usage) meant no code changes were required for either the 5→6 or 6→7 conceptual boundary. Full production build succeeded on the first attempt post-bump.
Typecheck tooling added (new, not previously present):
| Package | Version |
@astrojs/check | 0.9.9 |
typescript | 6.0.3 |
The site had no typecheck tooling installed before this pass. Added to bring cogs-site in line with sibling sites (hypernova-site, twf_site, fullstack-vc all run typescript@6.0.3) and to satisfy step 4 of the upgrade procedure (pnpm exec astro check).
Verification
pnpm run build— passes cleanly, 2 pages built, no errors.pnpm exec astro check— 0 errors, 0 warnings, 5 hints (all 5 hints are pre-existing unused-variable/destructure lint hints in section components, unrelated to this upgrade — left untouched per scope).The
[lightningcss minify]"Unknown at rule" warnings for@custom-variant,@theme,@applyseen during build are pre-existing Tailwind v4-syntax warnings from Vite's CSS minifier (not Astro-version-related) and were present before this upgrade too.
Not Touched (out of scope)
packageManager: "pnpm@10.17.0"pin inpackage.json— left as-is per instruction; flagged separately elsewhere.
Version
cogs-site bumped 0.0.2 → 0.0.3 (real dependency upgrade, not changelog-only).