Astro 7.4.12
Astro 7.4.12 landed on November 13, 2026, and it is a patch release in the truest sense: no new APIs, no config changes, three PRs in the changelog. But one of those three is a memory fix that large content-driven sites will feel, so it is worth the minute it takes to bump the version.
🧠 Memory Gets a Haircut
The headline change comes from Emanuele Stoppa: astro build now releases content collection entries from memory once the content layer sync finishes. If you run a site with thousands of Markdown or MDX entries, the build previously held onto every parsed entry for the whole run. Now those entries are dropped as soon as the sync step completes.
Nothing in your project changes. The payoff shows up as a lower peak memory number during builds, which matters most on CI runners with a fixed memory ceiling, or on a laptop that starts swapping when the build plus a dev server are both running. On small blogs you will not notice. On a documentation site with a deep content tree, this is the kind of fix that quietly stops a build from being killed at 4 GB.
📌 Integrations Get Their Range Back
Astro had pinned its own @astrojs/* dependencies to exact versions. Chris Swithinbank's change removes the pins so the ^ range applies again, which means a project can install a newer matching integration without waiting for a core release to loosen the constraint. The accompanying bumps in this release are @astrojs/markdown-satteri 0.4.10 and @astrojs/vite-plugin-astro 0.1.3.
The practical consequence: if you were stuck on an older integration because the core package insisted on an exact match, run your package manager's update and check whether the constraint now resolves upward. If you pin your own versions in package.json, nothing changes for you at all.
✏️ Typo Duty
The third change fixes a typo in the error message shown when an astro:font config has an invalid cssVariable. Pure polish, but welcome, since a garbled message in a config validation error is exactly where clarity matters most.
✅ Upgrade Check
This is a safe patch. No breaking changes, no deprecated flags, no lockfile movement beyond the dependency bumps. Update with your package manager, rebuild once, and confirm your content collections still sync. If your build machine was near its memory limit before, compare the peak usage this time around, because that is where 7.4.12 actually earns its place.