Astro 7.4.11
Overview
Astro 7.4.11 was published on November 11, 2026. It is the sixth patch release in the 7.4 line, following 7.4.9 and 7.4.10 from the previous day. The release contains no new APIs and no configuration removals. Its contents are seven behavior fixes plus a dependency refresh, with the largest share of work landing in host and forwarded-header validation for security.allowedDomains.
Projects on 7.4.x can upgrade with no code changes. Projects that terminate TLS behind a proxy and validate hosts through security.allowedDomains should read the validation section before updating, because acceptance rules for forwarded values are now stricter.
Security and Host Validation
Astro 7.4.11 changes how the framework reads X-Forwarded-Proto, X-Forwarded-Host and X-Forwarded-Port when security.allowedDomains is configured (PR #18641). The three forwarded values are now evaluated together against a single domain entry, rather than being checked one at a time.
- A forwarded protocol is applied only when the matched entry explicitly allows that protocol for the host in use.
- A forwarded port is applied only when the entry for that host lists the port.
- A forwarded host that arrives without a forwarded protocol is validated against the protocol of the server itself.
- An entry declared with
port: '443', or'80'for HTTP, now also matches a host header that omits a port. - Non-HTTP(S) forwarded protocol values such as
ftporwsare rejected when the allowlist mixes entries with and without aprotocolfield.
The same release tightens Host and X-Forwarded-Host parsing (PR #18641). Only a plain hostname with an optional port is accepted, and the validated host is written to Astro.url exactly as it was matched. Mixed patterns, unusual schemes, and values that previously slipped through partial checks will now fall back to rejection.
Dev Server and Preview
Malformed percent-encoded paths in the dev server and in static preview now return 400 Bad Request instead of bubbling up as a 500 (PR #18651). The practical effect is clearer diagnostics: a broken URL is reported as a bad request rather than appearing as an application crash in logs.
Build and Tooling Fixes
- Vite license files survive the build.
astro buildno longer deletes the license file emitted by Vite'sbuild.licenseoption. Astro now removes only its own Vite manifest from the.vite/output folder (PR #18686). This matters for projects that ship third-party license bundles in theirdistdirectory. - astro check error reporting. When
@astrojs/checkis installed but throws while loading, the command now surfaces the original error instead of claiming the package is missing and prompting for an install (PR #18672). - Scoped style spreading. Spreading the same object onto an element with scoped styles no longer mutates that object (PR #18629). Previously, an imported constant reused across renders accumulated scope classes in its
classproperty, growing on every request. Long-lived servers and static builds with repeated component renders were both affected.
Dependency Updates
Three internal packages moved with this release: @astrojs/markdown-satteri 0.4.9, @astrojs/runtime 0.1.1, and @astrojs/vite-plugin-astro 0.1.2. The markdown and Vite plugin bumps carry the scoped style fix described above.
Upgrade Notes
Upgrade with npm install [email protected], or the matching command for pnpm, yarn, or bun. Astro 7.4.11 requires Node.js 22.23.4 or newer and npm 9.6.5 or newer, unchanged from earlier 7.4 releases. If your deployment sits behind a reverse proxy, verify that every entry in security.allowedDomains lists the protocol and port your proxy actually forwards. Entries that relied on loose matching may need an explicit protocol or port value after this update.