AstroEco is Contributing…
Display your GitHub pull requests using astro-loader-github-prs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/solid-js@8.0.0
Major Changes
-
#17891
6fb274eThanks @ryansolid! - Adds support for Solid 2.0 (requiressolid-js@^2.0.0and@solidjs/web@^2.0.0)This major version supports Solid 2.0 only; use
@astrojs/solid-js@7(and@astrojs/solid-js-renderer@0.1) for Solid 1.x projects. The Solid 2.0 renderer lives in@astrojs/solid-js-renderer, which the integration re-exports.Highlights:
- Compiles through
@solidjs/vite-plugin(replacingvite-plugin-solid), with an optionalcompileroption to select the native or Babel backend. - Islands render through Solid 2.0's first-class async model (
renderToStream), with no Suspense wrapper: async islands settle fully on the server, and error boundaries (Errored) contain both sync and async errors. - Threads an asset manifest into server renders so
lazy()boundary modules inside islands resolve their module URLs, hydrate through serialized asset maps, and have their CSS inlined into the island markup (deduped per page) — in dev via the plugin's live resolver, in production via the client build manifest. - Component detection (
check()) now probe-renders through the stream renderer with per-component caching, rejects foreign framework vnodes explicitly, and no longer breaks on Proxy-based components. - Removes the
solid-devtoolsintegration option (the Solid 2.0 devtools story is not settled yet).
- Compiles through
Minor Changes
-
#17891
6fb274eThanks @ryansolid! - Adds support for Solid server components (experimental)Enable with
serverFunctions: { components: true }—"use server"functions that return a component, riding the server-function endpoint:// src/frames/panel.jsx 'use server'; export async function getPanel(name) { return (props) => ( <section> <h2>panel:{name}</h2> {props.children} </section> ); }
// inside an island const Panel = dynamic(() => getPanel(name()));
Server components render inline during island SSR and are adopted at boot with zero endpoint requests; re-evaluations stream over the endpoint and morph the boundary in place, preserving client slot state and DOM identity. The integration wires all the pieces: the frames render plugin and direct-call transform on the server, the endpoint response transform through the handler, and
installServerComponents()via Astro'sbefore-hydrationstage on the client. -
#17891
6fb274eThanks @ryansolid! - Adds support for Solid server functions (experimental)Enable with the
serverFunctionsoption (requires an adapter — server functions need a server at runtime):import { defineConfig } from 'astro/config'; import solid from '@astrojs/solid-js'; export default defineConfig({ integrations: [solid({ serverFunctions: true })], });
"use server"functions imported by Solid islands are compiled to typed RPC calls. The integration injects the transport endpoint (default/_server) as an Astro route, so server-function requests flow through Astro's middleware pipeline — the same auth guards andlocalsdecoration pages get — in dev and production alike. Inside a server function, Solid'sgetRequestEvent()exposes the request, Astro'slocals, and the full Astro API context asnativeEvent.Island SSR now also runs inside a Solid request-event scope, so
getRequestEvent()and direct in-process server function calls work during server rendering.Pass an options object instead of
trueto customize (endpoint path, argument codec, etc.) — it is forwarded to@solidjs/vite-plugin.
Patch Changes
- Updated dependencies [
6fb274e]:- @astrojs/solid-js-renderer@0.2.0
@astrojs/solid-js-renderer@0.2.0
Minor Changes
-
#17891
6fb274eThanks @ryansolid! - Adds support for Solid 2.0 (requiressolid-js@^2.0.0and@solidjs/web@^2.0.0)This major version supports Solid 2.0 only; use
@astrojs/solid-js@7(and@astrojs/solid-js-renderer@0.1) for Solid 1.x projects. The Solid 2.0 renderer lives in@astrojs/solid-js-renderer, which the integration re-exports.Highlights:
- Compiles through
@solidjs/vite-plugin(replacingvite-plugin-solid), with an optionalcompileroption to select the native or Babel backend. - Islands render through Solid 2.0's first-class async model (
renderToStream), with no Suspense wrapper: async islands settle fully on the server, and error boundaries (Errored) contain both sync and async errors. - Threads an asset manifest into server renders so
lazy()boundary modules inside islands resolve their module URLs, hydrate through serialized asset maps, and have their CSS inlined into the island markup (deduped per page) — in dev via the plugin's live resolver, in production via the client build manifest. - Component detection (
check()) now probe-renders through the stream renderer with per-component caching, rejects foreign framework vnodes explicitly, and no longer breaks on Proxy-based components. - Removes the
solid-devtoolsintegration option (the Solid 2.0 devtools story is not settled yet).
- Compiles through
astro@7.4.14
Patch Changes
- #17891
6fb274eThanks @ryansolid! - Updates the Solid tsconfig preset for Solid 2.0:astro add solid-jsnow writesjsxImportSource: "@solidjs/web"(renderer packages own their JSX namespaces andjsx-runtimetype entries in 2.0;solid-jsno longer exports one)

Fixes #18781.
Changes
- A sitemap chunk that rewrites a URL now keeps the original entry out of the default sitemap.
- The integration records which input entries matched and uses the callback's returned item for the named chunk. Returning the URL of a different page does not remove that other page from the default sitemap.
- A custom
pageschunk keeps its matched entries alongside unmatched entries insitemap-pages-0.xml.
The Factory preview addresses the original URL leak for named chunks. This patch also preserves the returned items when the chunk is named pages, where the default sitemap would otherwise overwrite them. Factory preview
Testing
- The chunked sitemap test covers an async callback that returns a copy with a rewritten URL. It checks both the named chunk and the default sitemap. A second case covers a custom
pageschunk.
Verification
The same fixture was built first with Astro 7.4.13 and @astrojs/sitemap 3.7.6, then with the patched integration. Minimal reproduction
Before, sitemap-pages-0.xml
https://example.com/
https://example.com/article/
After, sitemap-pages-0.xml
https://example.com/
The named chunk contains https://example.com/articles/current/ in both builds.
Docs
No docs change is needed. The existing docs already describe the default sitemap as containing URLs that did not match a chunk.

Changes
- tsconfig
pathsaliases (e.g.~/markdoc/...) used insidemarkdoc.config.*now resolve correctly instead of failing withCannot find package '~'. This regressed in 2.0.11 whenbundleConfigFile()switched from esbuild to Rolldown. - Replaced the bare
externalpredicate inload-config.tswith a Rolldownexternalize-depsplugin. The plugin resolves each bare import specifier before deciding whether to externalize it. Imports that resolve to a file inside the project root and outsidenode_modules(i.e. what a tsconfigpathsalias points to) are bundled; everything else stays external with its original specifier, matching the previous esbuild behavior.
Testing
- Added
packages/integrations/markdoc/test/units/load-config.test.tscovering the alias-resolution path: a config file that imports via a tsconfigpathsalias is bundled successfully, while true third-party package imports remain external.
Docs
- No docs update needed — this restores previously documented behavior with no API changes.
Closes #18779

Changes
- When
vite.build.cssMinifyorvite.build.minifyis set to"esbuild", Astro now detects at build start whether esbuild can be resolved from Vite and fails with a descriptiveMissingEsbuilderror — instead of surfacing Node's rawERR_MODULE_NOT_FOUND. This was broken by #18263, which removedesbuildas a direct Astro dependency; Vite 8 treats it as an optional peer, so projects that relied on hoisting now fail silently. - Implemented as a small Vite
buildStartplugin that checks resolvability before Vite attempts the import. No runtime overhead for projects that don't use esbuild minification.
Testing
- Added
packages/astro/test/units/build/plugin-esbuild-check.test.ts, which covers the cases wherecssMinify: "esbuild"orminify: "esbuild"is configured without esbuild installed (expects the new error) and where esbuild is resolvable (expects no error).
Docs
- No docs update needed; this is a developer-facing error message improvement with no new API surface.
Closes #18774

Changes
- Removes the
scrollendevent listener and the 50 ms polling fallback fromClientRouter. Both calledhistory.replaceState()on every frame of arequestAnimationFrame-driven scroll, which in Safari 26.2+ hits the browser's 100-writes-per-10-seconds limit and causes internal links to silently do nothing for 10 seconds. - Scroll positions are now kept in an in-memory map keyed by the router's history index and recorded only when an entry is left: in
transition(), in the Navigation APInavigateevent (coveringlocation.hashchanges and third-partypushStatecalls), and via a passivescrolllistener as a fallback for browsers without the Navigation API. The whole map is serialized tosessionStorageinpagehideand read back at init, so positions survive reloads and cross-document navigations.history.stateis kept as a fallback for entries created by older router versions.
Testing
- Added e2e tests in
packages/astro/e2e/view-transitions.test.tscovering: a rAF-driven scroll makes zerohistory.replaceState()calls; Back/Forward after a scripted scroll restores the correct position; reload after a traversal then Back restores correctly;location.hashchange then Back restores the pre-hash position; third-partypushStatethen Back.
Docs
- No docs update needed. This is an internal scroll-position bookkeeping change with no public API surface.
Closes #18761

Changes
- Removes the
fetch()fallback fromgetImageSize()in the dev toolbar audit. In Safari/WebKit, re-fetching an SVG that is currently animating freezes the animation; this was triggered forloading="lazy"images because WebKit reports all three resource timing size fields (decodedBodySize,encodedBodySize,transferSize) as0for lazy images. getImageSize()now reads size fromdecodedBodySize ?? encodedBodySize ?? transferSizeand skips the size check entirely when no size is available, rather than fetching. Eager images that are still loading are awaited; unloaded lazy images are skipped to avoid blocking the whole audit on below-the-fold content.
Testing
- Added an e2e test in
packages/astro/e2e/dev-toolbar-audits.test.tsasserting that opening the Audit app makes no extra network request for aloading="lazy"image, covering the WebKit-specific regression path in Chromium.
Docs
- No docs update needed; this is an internal dev-only audit behavior fix with no user-facing API changes.
Closes #18700

Changes
a11y-missing-contentno longer reports false positives for anchors insidevisibility: hiddencontainers or inside anaria-hidden="true"subtree. These elements are invisible to both sighted users and assistive technologies, so warning about their content is misleading and can produce thousands of spurious reports on sites that hide menus withvisibility: hidden.- Adds two early returns to the rule's
match(): one checking computedvisibility !== 'visible'(inherited, so covers hidden ancestors), and one checkingelement.closest('[aria-hidden="true"]'). Computed style is used instead ofcheckVisibility({ visibilityProperty: true })for broader browser compatibility.
Testing
- Extended the existing e2e dev-toolbar audit test (
packages/astro/e2e/dev-toolbar-audits.test.ts) with a new fixturea11y-hidden-anchor.astrocovering the two previously false-positive cases (visibility-hidden container and aria-hidden anchor) alongside the control cases. The visible-anchor-with-hidden-text warning introduced in #16016 is still reported.
Docs
- No docs update needed; this is a dev-only audit tool behavior fix with no public API impact.
Closes #18623

Changes
- Fixes island CSS that was missing or loaded twice when the same component is imported statically by one island and with
import()by another. This covers #18767 and the double load on pages that render both islands, without bringing back #18677. - The client build no longer decides globally whether to keep or delete a client CSS file. For each chunk, it walks up from the chunk's CSS modules to the hydrated components,
client:onlycomponents and scripts that load them, statically or throughimport(). It then adds the chunk's CSS to each of those pages, unless the page's server build already has all of it (cssScopeTo-aware, propagated content included). - Page-attributed CSS is removed from
importedCss, so Vite's preload never loads it again under another URL. Files no page links are deleted. CSS reachable only from entries not attributed to any page (e.g.injectScript('page')) keeps the old preload behavior. - Behavior change: CSS of modules that an island loads with
import(), where the server build can't see the import, now ships in the page HTML instead of loading when the import runs. This matches howclient:onlycomponents, scripts and server-visible dynamic imports already work. The preload list is shared by every page, so it can't skip a file only on the pages that already have its styles. - Replaces
shouldDeleteCSSChunk,getChunksSharedByIslands, thecssScopeTorestore path and theclient:onlyforce-inline workaround from #17292.
Testing
- Rewrote
css-deduplication.test.tsas a matrix overinlineStylesheetsnever,autoandalways. For every page it collects the head CSS plus whatever Vite's preload would add once all dynamic imports run, and asserts each style loads exactly once where expected and nowhere else. It also checks for missing files, CSS that only arrives through preload, and unused CSS files. - Added fixture pages for each historical case: #12303, #18677, #18678, #18767 (React, and the reporter's Svelte repro), both islands on one page, a lazy module sharing CSS with islands on other pages,
client:onlysharing a lazily loaded file, a server-visibleimport(), #16119, #18123 and #16251 (Svelte conditional rendering). Main fails 11 of the 60 checks, and the previous version of this PR failed 16. - The
'always'assertion goes back to "no CSS files are emitted", since every style is now inlined.
Docs
- No docs update needed: this is a build-output fix with no API or config changes.
Closes #18767

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.
Releases
@astrojs/cloudflare@15.0.0-beta.6
Patch Changes
- #18754
d342812Thanks @edmundhung! - Updates@cloudflare/vite-pluginto2.0.0-rc.0. Build output is now written to.cloudflare/output/v1/. Rebuild existing projects before runningastro previewor deploying withcf.

Changes
createAsyncManifestMemopreviously cached the pending promise indefinitely (evicting only on rejection). On Cloudflare Workers, a promise can only settle in the request that created it; if that request is cancelled while a shared load (middleware, session driver, cache provider, actions, or logger) is still in flight, the cached promise never settles and never rejects. Every subsequent request that awaits it throws "This promise was created by a request that has since ended", causing a burst of 500s until the isolate is recycled.- When a waiting caller's shared promise fails, the fix now removes the stale entry and retries the load once inside that caller's own request. Concurrent requests still share one in-flight load when nothing goes wrong, and a load that genuinely fails for all callers still rejects.
Testing
packages/astro/test/units/manifest/memo.test.tscovers the new retry path: a shared promise that rejects causes the waiting caller to evict the cache entry and start a fresh load, while a load that fails on every attempt still propagates the rejection.
Docs
- No docs update needed; this is an internal runtime fix with no public API change.
Closes #18764

Changes
getHeadings()andrender().headingsno longer turn{into${for.mdheadings when using theunified()processor. The.replace(/\{/g, '${')call inrehypeHeadingIdswas left over from 2021 when heading text was serialized into a JS template literal; headings are now serialized withJSON.stringify, so the escaping is both unnecessary and harmful.- One line removed from
packages/markdown/remark/src/rehype-collect-headings.ts. No change to rendered HTML or generated slugs.
Testing
- Added a regression test in
packages/markdown/remark/test/headings.test.tscovering a.mdheading that contains{to assert the returnedtextmatches the literal heading string.
Docs
- No docs update needed; this is a bug fix restoring already-documented behavior.
Closes #18716

Changes
ASTRO_DEV_BACKGROUND=0(andASTRO_PREVIEW_BACKGROUND=0) now correctly records"background": falsein the lock file. Previously,!!process.env.ASTRO_DEV_BACKGROUNDevaluated!!'0'astrue, making a foreground server appear as a background server and causingastro dev statusto reportbackgroundandastro dev logsto exit with "No log file found."- Introduces a small
isBackgroundServerProcess(envVar)helper incli/server.tsthat checksenv[envVar] === '1', matching the value the background spawner sets. Bothastro devandastro previewnow use this helper when writing the lock file.
Testing
- Adds
packages/astro/test/units/dev/background-env.test.tscovering theisBackgroundServerProcesshelper: verifies that=0, unset, and=1all produce the correct boolean so the lock file reflects the true server mode.
Docs
- No docs update needed; the existing Background mode documentation already describes the
=0opt-out correctly — only the implementation was wrong.
Closes #18719

Changes
- Fixes #18728. Since #18187, every platform-specific VSIX shipped only the runner's linux-x64-gnu
@astrojs/compiler-binding, so formatting failed withCannot find native bindingeverywhere else. - The extension is now published as one universal VSIX using the compiler's WASI build, like
astro2tsx. The new packaging step installs with--cpu=wasm32, runsvsce package, then reinstalls for the host becauseovsxneeds the native@node-rs/crc32. Both marketplaces publish that file with--packagePath.
Testing
- No test code added; this is a release workflow change.
Docs
- No docs update needed; this only affects how the extension is packaged.
Description
- Closes #1748
- Moves
<Banner />out of<main>inPage.astroso it sits above<TwoColumnContent />inside.main-frame. On wide viewports (>= 72rem) with a table of contents, the banner now spans the full width of the content area (both.main-paneand.right-sidebar-container) and appears centered instead of being constrained to.main-pane. - Updates
.right-sidebarsticky positioning inTwoColumnContent.astro(top: var(--sl-nav-height),height: calc(100vh - var(--sl-nav-height)), border moved onto.right-sidebar) so the right sidebar starts below the banner at scroll top and pins beneath the navbar when scrolling. - Adds
role="region"and a localizedaria-label(banner.accessibleLabel, seeded in built-in translation files sincebuiltinI18nSchema()requires all keys) toBanner.astroso the banner remains a unique accessible landmark outside<main>. - Updates
starlight-toc.tsto continue observing.sl-bannernow that it is no longer a descendant of<main>. - Adds Playwright E2E assertions covering banner alignment, landmark attributes, and sticky right-sidebar scroll behavior in
packages/starlight/__e2e__/basics.test.ts, plus an@astrojs/starlightpatch changeset.
Local verification after final edits:
- Build and publint check (
pnpm --filter '@astrojs/*' build) - Example build and
size-limitcheck (pnpm --filter @example/starlight-basics buildandpnpm size) prettier --checkon all modified files- Playwright E2E suite
__e2e__/basics.test.ts:52 passed - Targeted source and built
distVitest suites (i18n,translations,translations-fs,translations-ec,config-errors,starlight-page-route-data):84 passedin both source anddistmodes axe-playwrightaudit (wcag2a,wcag21a,wcag2aa,wcag21aa,wcag22aa,best-practice) on built/headings-banner/,/custom-page/, and/headings/pages:0violations

Changes
- Uses ephemeral ports for the custom entry file fixture so parallel test files cannot redirect requests to an unrelated port.
Testing
- Updates the preview and dev tests for the custom entry file to use an ephemeral port.
Docs
- No docs update is needed because this change only affects test setup.
AI was used to diagnose and implement this change.

Changes
@cloudflare/vite-plugin v2 and cf 1.0 are moving from beta to release candidates. This moves @astrojs/cloudflare on next from the plugin beta to its RC.
- Moves
@cloudflare/vite-pluginfrom an exact beta pin to^2.0.0-rc.0, which brings in the 1.0 RCs of@cloudflare/configand@cloudflare/build-output-utils. The exact pin protected against breaking changes between betas. RCs should not have breaking changes, so the range accepts later RCs and2.xwithout another bump, but not betas. - Replaces
ParsedInputConfigWithWorker, which the RC removes, withWorkerConfigandCloudflareConfig. - Reads Build Output from
.cloudflare/output/v1/instead ofv0/inastro previewand the tests. A build clears the whole.cloudflare/output/directory, so rebuilding removes any oldv0output. - Updates
cfin the adapter test fixtures andpackages/astro/e2e/fixtures/cloudflareto^1.0.0-rc.0, and exemptscf@1.0.0-rc.0fromminimumReleaseAge.
astro add @astrojs/cloudflare@beta needs no change. It installs cf@latest, and cf publishes its RC under latest.
This overlaps with #18742, which moves the same pin to 2.0.0-beta.v.17.
Testing
The existing adapter tests cover these code paths. They are updated for the v1 output paths and the renamed types. No new tests, because behavior is otherwise unchanged.
Docs
No docs change. Users don't configure or reference the Build Output path directly.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@7.4.13
Patch Changes
-
#18770
c850735Thanks @astro-factory! - Fixes the dev toolbar'sa11y-missing-contentaudit reporting anchors and headings that are hidden withvisibility: hiddenor are inside anaria-hidden="true"subtree -
#18536
d044365Thanks @KoenRijpstra! - Fixes server bundles including every renderable content collection entry when no server-rendered route callsrender()fromastro:content -
#18740
c7a2f1dThanks @astro-factory! - Fixesi18n.fallbackfailing withi18nNoLocaleFoundInPathwhen the fallback target is a locale defined with a custompath -
#18660
75ac226Thanks @NetBr3ak! - Fixes<Font preload>emitting no preload links when a requested weight range such as"400 700"sits inside a variable font file's range such as"400 900" -
#18758
273d7daThanks @astro-factory! - Fixesastro dev status,astro dev logs, and theastro previewequivalents treating a server started withASTRO_DEV_BACKGROUND=0orASTRO_PREVIEW_BACKGROUND=0as a background server -
#18658
33c931eThanks @hood! - Improves startup time of everyastrocommand for projects that don't configurefonts, by loading the font resolution dependencies only when fonts are used -
#18771
01c942dThanks @astro-factory! - Fixes the dev toolbar's audit fetchingloading="lazy"images again to measure them, which froze animated SVGs in Safari and downloaded images the page meant to load later -
#18711
bf5a170Thanks @astro-factory! - Fixes the dev server blocking cross-origin requests from an origin allowed by asecurity.allowedDomainsentry with a defaultport, such as{ hostname: 'staging.myapp.com', protocol: 'https', port: '443' }.BaseApp.validateForwardedHost()now applies the sameallowedDomainsrules as the rest of Astro. -
#18733
c6ab3c5Thanks @Marve10s! - Fixes hydration of framework components receiving sparse array props by serializing holes as undefined -
Updated dependencies [
c6ab3c5]:- @astrojs/runtime@0.1.2
@astrojs/cloudflare@14.4.9
Patch Changes
- #18720
d116e3dThanks @astro-factory! - Fixes a spuriousNo environment found in configurationwarning for the prerender worker when building withCLOUDFLARE_ENVset
@astrojs/node@11.1.14
Patch Changes
-
#18636
b4de3b5Thanks @umeraamir69! - Shares one processunhandledRejectionlistener across app handlers so standalone mode no longer treats in-request rejections as outside request context -
#18743
7c8dad5Thanks @EnesKartal! - AddsContent-Type: text/plain; charset=utf-8header to400responses for undecodable URLs in standalone mode.
@astrojs/sitemap@3.7.6
Patch Changes
- #18622
1dab71aThanks @Toyenzo! - Fixes i18n locale matching for pages whose first path segment is named like anObject.prototypeproperty, such as/constructor/or/toString/. These were treated as locales, producing invalid alternate links. Also rejects an i18ndefaultLocalethat is only an inherited object property rather than a configured locale.
astro-vscode@2.17.5
Patch Changes
- #18757
3ac5ad3Thanks @matthewp! - Fixes formatting.astrofiles failing withCannot find native bindingon Windows, macOS, and ARM or Alpine Linux
@astrojs/markdown-remark@7.3.10
Patch Changes
- #18759
387105bThanks @astro-factory! - FixesgetHeadings()andrender().headingsreporting{as${in Markdown heading text when using theunified()processor
@astrojs/runtime@0.1.2
Patch Changes

Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
Release Notes
withastro/compiler-rs (@astrojs/astro2tsx)
v0.1.4
Patch Changes
81881cb: Moves@emnapi/runtimefromdevDependenciestodependenciesso package managers that do not auto-install peer dependencies (e.g. Yarn 1) can load@astrojs/astro2tsxwithout a manual install.
withastro/compiler-rs (@astrojs/compiler-rs)
v0.5.3
Patch Changes
babel/babel (@babel/core)
v8.1.2
👓 Spec Compliance
babel-parserbabel-plugin-transform-regenerator,babel-plugin-transform-runtime- #18489 fix(regenerator): read the method of a member call before its arguments (@joellemd)
🐛 Bug Fix
babel-helper-module-transforms,babel-plugin-transform-dynamic-import,babel-plugin-transform-modules-amd,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-umd- #18589 Respect
importInterop: nonefor dynamic import (@nicolo-ribaudo)
- #18589 Respect
babel-parser- #18537 fix(parser): allow ASI between modifier-like field and @dec (@JLHwung)
- #18268 fix(parser): rework ts arrow param tracking (@JLHwung)
- #18524 fix(parser): record token location before checking reserved words (@JLHwung)
- #18533 fix(parser): reject arrow functions after an arrow in an earlier operand (@JLHwung)
- #18540 fix(parser): handle async do await in parameters (@JLHwung)
- #18515 fix(parser): start decorated object members at their first decorator (@JLHwung)
- #18484 fix(parser): allow TS imports to define exports declared before them (@JLHwung)
babel-helper-member-expression-to-functions,babel-plugin-transform-classes,babel-plugin-transform-object-super,babel-plugin-transform-private-methods- #18576 Keep the receiver of TS-wrapped
superand private member calls (@brunoborta)
- #18576 Keep the receiver of TS-wrapped
babel-helper-string-parser,babel-parserbabel-generator- #18570 fix(generator): keep parens that end an optional chain before (@joellemd)
- #18506 fix(generator): print override modifier of TSParameterProperty (@JLHwung)
- #18507 fix(generator): do not apply
jsescnumber radix to non-integer literals (@JLHwung) - #18430 fix(generator): escape
ofbinding of a using declaration in for-of head (@JLHwung)
babel-plugin-transform-class-static-blockbabel-templatebabel-helper-module-transforms,babel-parser,babel-plugin-transform-modules-commonjs,babel-plugin-transform-react-pure-annotations,babel-plugin-transform-typescript,babel-traverse,babel-typesbabel-plugin-transform-exponentiation-operator,babel-plugin-transform-logical-assignment-operators- #18527 fix memoise wrapped targets in logical assignment (@joellemd)
babel-plugin-transform-flow-commentsbabel-plugin-transform-block-scoping,babel-traversebabel-helpers,babel-plugin-transform-async-generator-functions,babel-plugin-transform-regenerator,babel-runtime-corejs3- #18557 fix(regenerator): dispatch pending jump after finally to outer finally blocks (@hoanle0126)
babel-traverse- #18551 fix(traverse): do not evaluate var s whose initializer may not have run (@joellemd)
babel-plugin-transform-regenerator- #18486 fix(regenerator): only remove bindings declared by the hoisted declar… (@joellemd)
babel-helper-module-transforms,babel-plugin-transform-modules-commonjs- #18498 fix: commonjs namespace re-export with a string export name (@bohdanprog)
🏠 Internal
- Other
babel-core,babel-helper-fixtures,babel-helper-transform-fixture-test-runner,babel-helpers,babel-node,babel-plugin-transform-runtime,babel-register,babel-template,babel-traverse,babel-types
🏃♀️ Performance
babel-parser- #18513 perf: Avoid allocating useless TS nodes (@liuxingbaoyu)
- #18423 perf(parser): general improvement (@JLHwung)
bombshell-dev/clack (@clack/prompts)
v1.9.0
Minor Changes
-
#596
cbeefcbThanks @dreyfus92! - Add accessible mode tospinner: when enabled via theaccessibleoption, the global setting, or theACCESSIBLEenv var, the spinner emits static, append-only, screen-reader friendly output, a plain start line, a "still working" heartbeat every 30 seconds, and a plain final line. Instead of animated in-place repaints. -
#614
5ac9e73Thanks @btea! - Allowmultiselectto accept readonly option arrays, e.g. options declared withas const. TheValuetype parameter is now inferred as a literal union ('a' | 'b') from such arrays, andinitialValuesalso accepts readonly arrays. -
#622
1835f41Thanks @btea! - Add support for disabledselectKeyoptions: they are rendered dimmed, cannot be selected by keypress, and are ignored when set as the initial value.
Patch Changes
-
#610
be35482Thanks @43081j! - Update sisteransi to 2.x (ESM only). -
#618
3e0bffdThanks @btea! - Use an explicit undefined check when forwarding autocomplete initialValue so 0, false, and empty strings remain selectable instead of falling back to the first option. -
#631
9053625Thanks @43081j! - Account for escape sequences i
[!IMPORTANT]
✂ PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

Summary
Fixes #18748.
When unifont's npm provider resolves installed fonts with remote: false, it returns local file: URLs (pathToFileURL(filePath).href).
Previously, CachedFontFetcher.fetch() only checked isAbsolute(url). Since file: URLs fail isAbsolute(url), they were routed to fetch(url). In Node.js, fetch() fails when attempting to fetch file: scheme URLs with TypeError: fetch failed / CannotFetchFontFile.
Changes
- In
packages/astro/src/assets/fonts/infra/cached-font-fetcher.ts, checkurl.startsWith('file:')and convert to a local filesystem path usingfileURLToPath(url). - Forward the converted path to the configured
#readFile()handler. - Added unit test in
packages/astro/test/units/assets/fonts/infra.test.ts. - Included changeset.

Changes
Fixes #18744
In astro dev, using a custom Cloudflare Worker entrypoint with FetchState and the documented companion handler:
export default {
async fetch(request: Request, env: Env, ctx: ExecutionContext) {
const state = new FetchState(request);
const asset = await cf(state, env, ctx);
if (asset) return asset;
return finalize(state, await astro(state));
},
};caused every page with export const prerender = true to return 404.
Root Cause
- In production, prerendered pages are emitted as static assets, and
fallbackToAssetsserves them. - In
astro dev, static assets have not been built to disk.FetchStateconstructed from a bare request in a custom entrypoint lacks pre-populated render options, so it resolves routes with the production matcher which skips prerendered routes whenmanifest.serverLikeis true, falling back to the 404 route. - The adapter's default entrypoint calls
app.devMatch()in dev mode, which allows prerendered routes.
Solution
In packages/integrations/cloudflare/src/fetch.ts, when app!.isDev(), match the request pathname using await app!.devMatch(app!.getPathnameFromRequest(state.request)) and assign state.routeData = result.routeData.
Added changeset .changeset/cloudflare-fetch-dev-prerender.md (@astrojs/cloudflare patch).
Testing
Verified with the reproduction from #18744:
- In
astro dev, visiting/(prerender = true) returns 200 with rendered page content instead of 404. - On-demand SSR routes (
/ssr) and fallback asset handling continue to function as expected.
Docs
No documentation changes needed.

Fixes #18739
Changes
- Added an optional
beforeSwaphook todoSwap()inpackages/runtime/src/internal/transitions/events.ts, invoked afterastro:before-swapandafterDispatch(fallback old-page animation) and immediately beforeevent.swap(). - Split
moveToLocation()inpackages/astro/src/transitions/router.tsintowriteHistoryEntry()(run inbeforeSwapsolocation.hrefandhistory.stateare updated beforeevent.swap()inserts the new DOM and triggers custom elementconnectedCallback()) andscrollToLocation()(run afterdoSwap()once the new DOM is in place). - Removed the now-unnecessary
pageTitleForBrowserHistorytemporary title juggling sincewriteHistoryEntry()runs beforeevent.swap()overwritesdocument.title(and intra-page hash navigation keeps the same title). - Added a Playwright e2e regression test in
packages/astro/e2e/view-transitions.test.tsverifying that custom elements upgraded during swap see the new URL andhistory.state,astro:before-swapstill sees the previous URL, andhistory.replaceState()insideconnectedCallback()updates the new entry without overwriting the previous page's entry.
Verification
pnpm run build:ci(34/34 packages built)pnpm exec playwright test e2e/view-transitions.test.ts -g "custom elements upgraded during swap|history" --reporter=list(5 passed)pnpm --filter @astrojs/runtime test(8 passed)pnpm --filter astro test:types(passed)pnpm exec biome ci --formatter-enabled=false packages/runtime/src/internal/transitions/events.ts packages/astro/src/transitions/router.ts packages/astro/e2e/view-transitions.test.ts(0 errors)

Changes
Fixes #18739
During a <ClientRouter /> navigation, updateDOM previously executed doSwap() (and event.swap(), inserting the new DOM into document) before calling moveToLocation(), which writes the history entry.
Because inserting the new page synchronously upgrades and connects custom elements on it whose definitions are registered, their connectedCallback runs immediately and reads location and history.state of the previous page.
Furthermore, if a component writes to the URL during initialization (e.g. history.replaceState(...)), it overwrote the previous page's history entry, causing moveToLocation to find to.href === location.href and push nothing, corrupting browser history.
Solution
- Add an optional
beforeInsert?: (event: TransitionBeforeSwapEvent) => voidhook todoSwapinpackages/runtime/src/internal/transitions/events.ts. - In
packages/astro/src/transitions/router.ts:- Split history entry writing into
writeHistoryEntry(to, options, historyState). - Pass a
beforeInsertcallback todoSwapthat setsdocument.title = pageTitleForBrowserHistory, callswriteHistoryEntry, and restores title right beforeevent.swap(). - Pass
historyWritten = truetomoveToLocationafter swap so that only scroll restoration / hash positioning runs post-swap.
- Split history entry writing into
- Added changeset
.changeset/swap-history-before-insert.md(astroand@astrojs/runtimepatch).
Testing
Verified with the reproduction from #18739:
- Direct load on
/b/?x=1shows/b/?x=1. - Navigation from
/a/to/b/?x=1now properly provides/b/?x=1to the<url-reader>custom element during itsconnectedCallback. - Navigation from
/a/to/c/with custom element callingreplaceStateretains/a/in history, allowing Back navigation to return to/a/.
Docs
No documentation changes needed; this fixes internal ordering so that custom elements during client-side navigation observe standard page-load URL state.

Fixes #18689
Changes
- Added
Content-Type: text/plain; charset=utf-8header to the400 Bad request.response increateStandaloneHandler(packages/integrations/node/src/standalone.ts) whendecodeURI(req.url)throws. - Added unit test
packages/integrations/node/test/units/standalone-handler.test.tscovering undecodable paths (/%C0%AF) and query strings (/?q=100%). - Added a patch changeset for
@astrojs/node.
Testing
pnpm --filter @astrojs/node build(passed)pnpm --filter @astrojs/node exec astro-scripts test test/units/*.test.ts(11/11 passed)pnpm --filter @astrojs/node exec astro-scripts test test/bad-urls.test.ts(2/2 passed)

Changes
Renaming a glob() content file with the same slug and contents leaves its old path cached and can break builds. Include the relative file path in the digest to refresh the entry and deferred import.
Testing
Content-layer tests (126) and Markdoc tests (2) passed. Regression tests cover eager and deferred rendering. Build, type and changed-file lint checks passed.
Docs
Existing file-renaming behavior is restored.

Changes
optimizeFallbacks()now selects the most representative file for metric measurement before callingCapsizeFontMetricsResolver.getMetrics(). It prefers Latin subset, then normal style, then the weight closest to 400. Previously the resolver cached by family name and used whichever file the provider returned first—for Montserrat on Google that was Cyrillic and/or italic—sosize-adjustvaried with subset order and was wrong for Latin text.- With the fix,
size-adjustfor Montserrat is 112.83% regardless of which subsets or styles are configured, matching the value measured on rendered text in Chromium.
Testing
- Extended
packages/astro/test/units/assets/fonts/core.test.tswith cases covering Latin-only, Latin+Cyrillic, and Cyrillic+Latin configurations to assert thatsize-adjustis identical across all three and corresponds to the Latin upright 400 file.
Docs
- No docs update needed; this is a correctness fix to an internal metric-selection step with no API or configuration surface change.
Closes #18736

Changes
- Cached routes returning 204, 205, or 304 no longer cause a 500 on cache hits.
createResponseFromCacheEntry()now passesnullas the body for null-body statuses ([101, 204, 205, 304]), matching the same list already used incore/app/prerender.ts. Previously, the emptyArrayBufferstored on a cache miss was passed to theResponseconstructor, which the runtime rejects for these status codes, causing every hit (including SWR/stale reads) to throw and return a 500 until the entry expired. - The failing entry was not evicted after the error, so 500s repeated on every request until TTL elapsed.
Testing
- Added unit tests in
packages/astro/test/units/cache/memory-provider.test.tscovering cache hits for 204, 205, and 304 responses, verifying the correct status is returned and no error is thrown.
Docs
- No docs update needed; this is a bug fix for existing documented behavior.
Closes #18721
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/starlight@0.43.1
Patch Changes
- #4396
46a5020Thanks @trueberryless! - Fixes a regression where the icon of the<Aside>component was rendered smaller than the icon of Markdown asides.
Description
This PR fixes a small regression introduced in #4190 I believe, where the icon of an <Aside> component is rendered smaller than the icon of a Markdown aside (:::note). It does so by specifically setting size="1.333em" on the Aside icon and also adding a regression test with fixture for the future.
- Closes #4395
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| peter-evans/create-pull-request | action | patch | v8.1.2 → v8.1.3 |
Release Notes
peter-evans/create-pull-request
v8.1.3: Create Pull Request v8.1.3
What's Changed
- fix: check git ref directly when pushing signed commits by @peter-evans in #4521
- Update distribution by @actions-bot in #4526
Full Changelog: peter-evans/create-pull-request@v8.1.2...v8.1.3
Configuration
📅 Schedule: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/starlight@0.43.0
Minor Changes
-
#4190
3f2336bThanks @delucis! -⚠️ BREAKING CHANGE: Adds support for any AstroscopedStyleStrategyconfiguration.Previously, Starlight forced the
"where"strategy, resulting in CSS selectors like:where(.astro-HASH). Starlight now respects the strategy set inastro.config.mjsand will default to Astro’s default"attribute"strategy, resulting in attribute selectors like[data-astro-cid-HASH].The new default can change some styling behaviour, so we recommend checking for visual changes in your site when updating. In particular, note the following:
-
Attribute selectors have a higher specificity than
:where()selectors. Check to ensure styles still apply and no CSS changes are needed to ensure the relative specificity of declarations remains the same. -
Astro’s
"attribute"strategy does not automatically pass along a parent component’s scope when passing aclassdown to a child component. If you have components that depended on this, you will need to update the child component to spread the parent’s data attribute where you are reusing the class name, for example:--- // Parent.astro --- <Child class="special-case" /> <style> .special-case { --accent-color: red; } </style>
--- // Child.astro -const { class: className } = Astro.props; +const { class: className, ...attributes } = Astro.props; --- -<div class={className}> +<div class={className} {...attributes}> <!-- ... --> </div>
See “Passing a
classto a child component” in the Astro docs for more details.
Alternatively, if you wish to continue using the previous scoping strategy in your site, set it explicitly in your Astro configuration file:
// astro.config.mjs import { defineConfig } from 'astro/config'; export default defineConfig({ + scopedStyleStrategy: "where", // ... }); -
-
#3674
993ac27Thanks @controversial! - Adds support for Pagefind’sexcludeSelectorsandincludeCharactersconfiguration to customize how search indexes are built -
#4219
35abe4fThanks @delucis! - Refactors Starlight’s theme select menu to reduce its JavaScript use⚠️ Potentially breaking change: If your project or theme plugin overrides theThemeSelectcomponent, check that it still works after updating. The global API previously used by theme select components has been removed and callingStarlightThemeProvider.updatePickers()will no longer work.See
ThemeProvider.astro,ThemeSelect.astro, andLanguageSelect.astroon GitHub for the full source code of the updated components. -
#4385
c130349Thanks @delucis! - Updates dependencyi18nextto v27⚠️ Potentially breaking change: If you use Starlight’s translation APIs directly, see i18next’s migration guide for details. We don’t expect any changes to impact Starlight users, but let us know if they do.
Patch Changes
Description
- Closes #4389
getAsideIconName()checked a custom aside icon with!Icons[iconName], which also matches properties inherited fromObject.prototype. Icon names such asconstructor,toStringor__proto__were accepted. With the default Markdown processor, the aside's<svg>then contained text likefunction Object() { [native code] }. Withunified(), the build failed with a generic parse error instead of "Invalid aside icon".- The check now uses
Object.hasOwn(Icons, iconName), the same approach as #4309 for autogenerated sidebars. This covers Markdown asides (both processors) and the<Aside>component, which sharegetAsideIconName(). - Nothing visual changes for valid icons.
Tests:
- New
__tests__/basics/aside-utils.test.ts: covers default, valid and unknown icons, and checks thatconstructor,toString,hasOwnPropertyand__proto__throw "Invalid aside icon". The 4 prototype cases fail onmain. __tests__/markdown-processor/asides.test.ts: rendering:::note{icon="constructor" | "toString" | "__proto__"}now throws on both processors. Onmain, the satteri cases render instead of throwing.- The full
@astrojs/starlightunit suite passes (693 tests), and Prettier and ESLint are clean on the changed files. - Changeset:
@astrojs/starlightpatch.

Fixes #18732. This replaces #18431, which was closed for lack of an issue; the issue now has a minimal reproduction: https://github.com/Marve10s/astro-sparse-array-props-repro
Changes
- Sparse array props stop framework components from hydrating.
Array(2)passed as{ items: Array(2) }serializes as{"items":[1,[null,null]]}, and the island decoder throwsTypeError: t is not iterableon the barenullentries. Array.prototype.mapskips holes.serializeArrayin@astrojs/runtimenow usesArray.from, which visits every index, so each hole goes through the existing serializer asundefinedand comes out as[0]:{"items":[1,[[0],[0]]]}.- The wire format and the client island script are unchanged. A hole and an explicit
undefinedentry now serialize the same way.
Testing
- Two regressions in
packages/astro/test/serialize.test.tscover a sparse array and a nested sparse array. Both fail onmainand pass with the fix; all 27 serializer tests pass. - I rebuilt the reproduction against Astro 7.4.11 with the patched serializer and loaded it in headless Chromium. Before the fix the island stays unhydrated and logs
[hydrate] Error parsing props; after it, the component hydrates and the console has no errors. - Biome and Prettier pass on the changed files. I did not run the full test, typecheck, or e2e suites locally.
Docs
No docs change. Arrays are already supported as hydrated props, and this fixes their serialization without adding an API. A patch changeset covers astro and @astrojs/runtime.

Changes
- When
CLOUDFLARE_ENVis set duringastro build, the prerender worker's Vitepreview()server would pass that env name to wrangler while reading the already-resolveddist/server/.prerender/wrangler.json. Because that generated config has noenvsections (they were already merged during the main build), wrangler emitted a misleading "No environment found" warning for every build. The fix clearsprocess.env.CLOUDFLARE_ENVto''only for the duration of the prerender preview server startup, then restores the original value. The prerendered pages still receive the correct environment variables because the config was already resolved before this step. - Using
''instead ofdeleteensures that aCLOUDFLARE_ENVvalue coming from a.envfile is also suppressed during this window.
Testing
- Adds
packages/integrations/cloudflare/test/prerender-cloudflare-env.test.ts, which builds a fixture withCLOUDFLARE_ENVset and asserts that the warning does not appear in the build output.
Docs
- No docs update needed; this is a build-time warning fix with no user-facing API or configuration change.
Closes #18712

Changes
errors-data.ts moved to packages/runtime/src/internal/core/errors/ in #18610, but the follow-up edits in that PR point at packages/runtime/src/core/errors/errors-data.ts, which does not exist.
Update the remaining references to the real path: the ESLint config for the docs-generation file, the docs path filter and docs pr labeler, plus the two Markdown links and the AGENTS.md path.
Testing
packages/runtime/src/core/errors/errors-data.ts returns 404 and packages/runtime/src/internal/core/errors/errors-data.ts exists on main. No code or behavior changes, only path strings.
Docs
No user-facing docs change and no changeset, this only corrects internal paths and links.
Description
- Updates i18next to v27, the recently released new major version — might as well before v1 to not be too far behind
- The breaking changes in this release seem to be minimal: https://www.i18next.com/misc/migration-guide (it’s a bit hard to read — not the most helpful guide I’ve ever encountered)
- I chose to reverse the
returnEmptyStringchange, which would be hard for users to work around if they were depending on it, whereas the v26 behaviour gives users more options. - Otherwise, I think the changes should be not noticeable (and certainly not to most users who do not use our translation APIs directly).
- There is one change in a test due to i18next no longer escaping
/in strings. The migration guide shows how to restore the old behaviour, but I don’t see why we would have to escape/so I decided to accept this change.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@7.4.12
Patch Changes
-
#18409
2917650Thanks @matthewp! - Fixes a typo in the error message shown when a fontcssVariableis invalid -
#18709
6f1a2a8Thanks @ematipico! - Reduces memory usage duringastro buildby releasing content collection entries from memory once the content layer sync is complete. -
#18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed -
Updated dependencies [
59052e7]:- @astrojs/markdown-satteri@0.4.10
- @astrojs/vite-plugin-astro@0.1.3
create-astro@5.3.2
Patch Changes
-
#17477
a475ac0Thanks @alexanderdombroski! - Fixes create astro to use correct project name when creating in current directory "." -
#17487
3cb7043Thanks @colinhacks! - Adds support for the nub package manager
@astrojs/cloudflare@14.4.8
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/markdoc@2.1.5
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/mdx@8.1.6
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed - Updated dependencies [
59052e7]:- @astrojs/markdown-satteri@0.4.10
@astrojs/netlify@8.2.14
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/node@11.1.13
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/preact@6.1.6
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed - Updated dependencies [
59052e7]:- @astrojs/preact-renderer@0.1.3
@astrojs/react@7.1.9
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed - Updated dependencies [
59052e7]:- @astrojs/react-renderer@0.1.3
@astrojs/sitemap@3.7.5
Patch Changes
- #18149
71f4d06Thanks @irontaek! - Speeds up sitemap chunk generation for large sites by tracking assigned URLs with a Set.
@astrojs/solid-js@7.1.6
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed - Updated dependencies [
59052e7]:- @astrojs/solid-js-renderer@0.1.2
@astrojs/svelte@9.1.6
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed - Updated dependencies [
59052e7]:- @astrojs/svelte-renderer@0.1.2
@astrojs/vercel@11.0.22
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/vue@7.1.6
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed - Updated dependencies [
59052e7]:- @astrojs/vue-renderer@0.1.2
@astrojs/markdown-remark@7.3.9
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/markdown-satteri@0.4.10
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/preact-renderer@0.1.3
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/react-renderer@0.1.3
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/solid-js-renderer@0.1.2
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/svelte-renderer@0.1.2
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/vue-renderer@0.1.2
Patch Changes
- #18713
59052e7Thanks @delucis! - Unpins@astrojs/*dependencies to allow versions matching the^range to be installed
@astrojs/vite-plugin-astro@0.1.3
Patch Changes
This PR contains the following updates:
| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| peter-evans/create-pull-request | action | patch | v8.1.1 → v8.1.2 |
v8.1.3 |
Release Notes
peter-evans/create-pull-request
v8.1.2: Create Pull Request v8.1.2
What's Changed
- Update distribution by @actions-bot in #4361
- build(deps-dev): bump the npm group with 2 updates by @dependabot[bot] in #4372
- refactor: replace
uuiddep with Node.js built-incrypto.randomUUIDby @peter-evans in #4377 - build(deps): update to jest 30 by @peter-evans in #4388
- build(deps-dev): bump the npm group across 1 directory with 7 updates by @dependabot[bot] in #4391
- build(deps-dev): bump undici from 6.25.0 to 6.27.0 by @dependabot[bot] in #4386
- build(deps-dev): bump js-yaml from 4.2.0 to 5.0.0 by @dependabot[bot] in #4387
- chore: pin actions to commit shas by @peter-evans in #4406
- build(deps): bump actions/checkout from 6.0.3 to 7.0.0 in the github-actions group by @dependabot[bot] in #4411
- build(deps-dev): bump the npm group with 2 updates by @dependabot[bot] in #4418
- build(deps-dev): bump js-yaml from 5.2.0 to 5.2.1 by @dependabot[bot] in #4423
- build(deps-dev): bump js-yaml from 5.2.1 to 5.2.2 by @dependabot[bot] in #4430
- build(deps-dev): bump the npm group with 4 updates by @dependabot[bot] in #4436
- build(deps): bump the github-actions group with 2 updates by @dependabot[bot] in #4435
- build(deps): bump brace-expansion by @dependabot[bot] in #4446
- build(deps-dev): bump the npm group with 4 updates by @dependabot[bot] in #4452
- Update distribution by @actions-bot in #4457
- build(deps-dev): bump browserslist from 4.28.4 to 4.28.8 by @dependabot[bot] in #4462
- build(deps-dev): bump js-yaml from 4.2.0 to 5.4.2 by @dependabot[bot] in #4468
- build(deps-dev): bump undici from 6.28.0 to 6.29.0 by @dependabot[bot] in #4478
- build(deps-dev): bump the npm group with 4 updates by @dependabot[bot] in #4483
- build(deps): bump brace-expansion by @dependabot[bot] in #4486
- build(deps-dev): bump handlebars from 4.7.9 to 4.7.10 by @dependabot[bot] in #4494
- build(deps-dev): bump undici from 6.29.0 to 6.29.1 by @dependabot[bot] in #4504
- build(deps): bump the github-actions group with 3 updates by @dependabot[bot] in #4510
- build(deps-dev): bump the npm group with 4 updates by @dependabot[bot] in #4509
- Fix submodule deletion with
sign-commitsby @MrSubidubi in #4473
New Contributors
- @MrSubidubi made their first contribution in #4473
Full Changelog: peter-evans/create-pull-request@v8.1.1...v8.1.2
Configuration
📅 Schedule: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

Changes
- Switches from
workspace:*toworkspace:^in package dependencies - This means that instead of publishing e.g.
"@astrojs/internal-helpers": "0.13.2", we ship"@astrojs/internal-helpers": "^0.13.2"allowing users to update within the^version range if newer versions of the package are available. - This can matter, because sometimes we’ll update package A, but another package B that depends on A is not published. In this case, package B will never be able to use the updates from package A, and users can end up with duplicates or stuff can even break.
- Recent example:
@astrojs/markdown-satteriupdated thesatteriversion it uses to v0.11, but@astrojs/mdxwas never published. This meant@astrojs/mdxwas pinned to using an older version of@astrojs/markdown-satteri, preventing MDX users from updating.
Testing
- Existing tests should pass
- Bit hard to test if there is a real downstream impact that could break due to a newer version of a dep now being used, but given we test with latest in the monorepo, I don’t foresee that.
Docs
n/a
Description
This PR updates Lunaria and its GitHub Action to their latest versions to handle pull_request_target being blocked by default.
The new setup uses the new documented 2 workflow approach relying on the workflow_run event to run Lunaria after the Lunaria Trigger workflow completes.
From my understanding, here are the changes we should observe (not issues, just listing them):
- Lunaria comments on PRs from first-time contributors will only appear after we approve the workflow runs for the PR whereas before they appeared immediately.
- The list of checks won't include Lunaria (only the trigger, so if Lunaria fails, the Actions tab will be the only place to see the failure).
- We cannot test without merging this PR first.
Afaik, the changes to @lunariajs/core should not affect us.

Changes
astro devno longer blocks cross-origin requests whoseallowedDomainsentry specifies a default port (e.g.port: '443'withprotocol: 'https'orport: '80'withprotocol: 'http'). The URL parser normalises default ports to'', so the previousmatchPattern-based check inBaseApp.validateForwardedHostcould never match them.BaseApp.validateForwardedHostnow delegates tovalidateHost(the same helper used everywhere else since #18641), making the dev-server Sec-Fetch check and the public helper consistent with the documentedallowedDomainsrules. The unusedmatchPatternimport is removed.
Testing
- New unit test cases in
packages/astro/test/units/dev/sec-fetch.test.tscover origins matched by entries withport: '443'/port: '80', confirming they pass the Sec-Fetch check; evil origins remain blocked.
Docs
- No docs update needed — the fix aligns the implementation with the already-documented behaviour of
allowedDomains.
Closes #18710

Fixes #18708
Changes
astro buildreleases the content layer once its sync is done. Before, theglobalContentLayersingleton kept a reference to it, so the data store, holding every loaded entry, stayed in memory for the rest of the build, including while pages prerender.- The build sync calls
globalContentLayer.dispose()instead ofcontentLayer.dispose(). It still disposes the content layer, and also clears the singleton. Dev keeps its content layer, because it passesskip.cleanup. - With 5,000 entries of ~20 KB, the heap at
astro:build:donedrops from 143 MB to 47 MB. The reproduction is in #18708.
Testing
- Adds
test/units/content-layer/sync-cleanup.test.ts: after a build sync,globalContentLayer.get()isnull. Withskip.cleanup: true, the content layer is kept.
Docs
- No docs update needed: this changes memory usage only, not behavior.
Description
Adds an AWS logo to the grid on the landing page.
IIRC, I’d seen AWS usage of Starlight before, but couldn’t track it down when adding the logo grid, but I spotted https://aws.github.io/graph-explorer/ today.
Description
- Adds Zeku to the community tools and integrations list on the Plugins and Integrations page.
- Zeku is a desktop app for writing in a Starlight or Astro project. It opens the project's content folder, reads the collection schema for its frontmatter forms, and knows Starlight's own frontmatter, asides, components, sidebar labels, and badges. Plain files, published with your own git.
- It's a paid app with a 14-day free trial, which the card says, so readers know before clicking.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@7.4.11
Patch Changes
-
#18641
08e2ceeThanks @astro-factory! - Validates the protocol, host and port fromX-Forwarded-Proto,X-Forwarded-HostandX-Forwarded-Porttogether against eachsecurity.allowedDomainsentry, instead of one at a time:- A forwarded protocol is only applied when an entry allows it for the host in use.
- A forwarded port is only applied when the entry for that host lists it.
- A forwarded host without a forwarded protocol is validated with the protocol of the server.
- An entry with
port: '443'(or'80'forhttp) now matches a host that doesn't include a port.
-
#18651
93a9057Thanks @umeraamir69! - Returns 400 Bad Request for malformed percent-encoded paths in the dev server and static preview instead of bubbling into a 500 -
#18672
e901468Thanks @astro-factory! - Fixesastro checkreporting@astrojs/checkas missing when the package is installed but throws while loading. The original error is now shown instead of an install prompt. -
#18641
08e2ceeThanks @astro-factory! - Fixessecurity.allowedDomainsaccepting non-HTTP(S)X-Forwarded-Protovalues (such asftporws) when the list mixes patterns with and without aprotocol -
#18686
62bb716Thanks @astro-factory! - Fixesastro builddeleting the license file generated by Vite'sbuild.licenseoption. Astro now removes only its own Vite manifest from the.vite/output folder. -
#18629
e9916e1Thanks @decrek! - Fixes spreading an object onto an element with scoped styles changing that object. When the same object was spread on every render, for example a constant imported from another module, itsclassgrew with every request. -
#18641
08e2ceeThanks @astro-factory! - Tightens howsecurity.allowedDomainsvalidates theHostandX-Forwarded-Hostheaders. Only a plain hostname with an optional port is accepted, and the validated host is applied toAstro.urlexactly as it was matched. -
Updated dependencies [
d13beeb,e9916e1]:- @astrojs/markdown-satteri@0.4.9
- @astrojs/runtime@0.1.1
- @astrojs/vite-plugin-astro@0.1.2
@astrojs/mdx@8.1.5
Patch Changes
- Updated dependencies [
d13beeb]:- @astrojs/markdown-satteri@0.4.9
@astrojs/preact@6.1.5
Patch Changes
- Updated dependencies []:
- @astrojs/preact-renderer@0.1.2
@astrojs/react@7.1.8
Patch Changes
- Updated dependencies []:
- @astrojs/react-renderer@0.1.2
@astrojs/solid-js@7.1.5
Patch Changes
- Updated dependencies []:
- @astrojs/solid-js-renderer@0.1.1
@astrojs/svelte@9.1.5
Patch Changes
- Updated dependencies []:
- @astrojs/svelte-renderer@0.1.1
@astrojs/vue@7.1.5
Patch Changes
- Updated dependencies []:
- @astrojs/vue-renderer@0.1.1
@astrojs/markdown-remark@7.3.8
Patch Changes
- #18698
d13beebThanks @astro-factory! - Fixes MDXoptimizeemptying<style>and<script>elements nested in static HTML from plugins, and turning SVG attributes likemarker-endintomarkerEndwhenignoreElementNamesis set
@astrojs/markdown-satteri@0.4.9
Patch Changes
- #18698
d13beebThanks @astro-factory! - Fixes MDXoptimizeemptying<style>and<script>elements nested in static HTML from plugins, and turning SVG attributes likemarker-endintomarkerEndwhenignoreElementNamesis set
@astrojs/preact-renderer@0.1.2
Patch Changes
- Updated dependencies [
e9916e1]:- @astrojs/runtime@0.1.1
@astrojs/react-renderer@0.1.2
Patch Changes
- Updated dependencies [
e9916e1]:- @astrojs/runtime@0.1.1
@astrojs/solid-js-renderer@0.1.1
Patch Changes
- Updated dependencies [
e9916e1]:- @astrojs/runtime@0.1.1
@astrojs/svelte-renderer@0.1.1
Patch Changes
- Updated dependencies [
e9916e1]:- @astrojs/runtime@0.1.1
@astrojs/vue-renderer@0.1.1
Patch Changes
- Updated dependencies [
e9916e1]:- @astrojs/runtime@0.1.1
@astrojs/runtime@0.1.1
Patch Changes
- #18629
e9916e1Thanks @decrek! - Fixes spreading an object onto an element with scoped styles changing that object. When the same object was spread on every render, for example a constant imported from another module, itsclassgrew with every request.
@astrojs/vite-plugin-astro@0.1.2
Patch Changes
- Updated dependencies [
e9916e1]:- @astrojs/runtime@0.1.1

Changes
- Raw
<style>and<script>elements whose text content was moved into aset:htmlproperty byrehypeCollapseScriptStyleare now excluded from the static optimizer, preventing their content from being written as a literal attribute (<style set:html="…"></style>). This affects both the unified and Sätteri processors. - In the unified optimizer (
rehype-optimize-static.ts), elements that carry aset:html/set:textdirective are treated as non-static, so they and their siblings fall through to the runtime path. The optimizer also now passesspace: 'svg'when serializing static children that sit inside an<svg>context (stopping at<foreignObject>), fixing camelCased attribute names likemarkerEnd→marker-end. - In Sätteri (
create-processor.ts),scriptandstyleare always added tooptimizeStatic.ignoreElementsalongside any user-suppliedignoreElementNames, matching the unified fix.
Testing
- Added cases to
packages/markdown/remark/test/mdx-rehype-optimize-static.test.tscovering raw<svg><style>withoptimize: trueandignoreElementNames: ["style"], including a<div><style>…</style><p>…</p></div>case with<and&in CSS to verify content is not escaped. - Added cases to
packages/markdown/satteri/test/mdx-renderer-options.test.tscovering the same scenarios for the Sätteri processor.
Docs
- No docs update needed; this is a bug fix restoring already-documented behavior for
optimize: true.
Closes #18652

Changes
- Adds a changeset for the
@astrojs/internal-helpers/rendererexport added in #18612. The framework integrations were published requiring@astrojs/internal-helpers@0.13.1, which lacks it.
Testing
changeset statusbumps@astrojs/internal-helpersand the five integrations.
Docs
- None.
Description
- Removes the guidance to set
nodejs_compatfor Cloudflare users. Since August, Node compat has been enabled by default (see “Node.js compatibility” in the Cloudflare docs), so this guidance is only really needed for people with older projects trying to add Starlight. Given that’s likely a fairly small population and we don’t generally cover platform-specific stuff unless really necessary, I think it makes sense to clean that up. (As this is a standalone paragraph, I also went ahead and removed it from translations.) - While in there, I also removed the CF docs from the showcase sites since they no longer use Starlight.
Description
- This PR updates the link cards used in our docs to link to external content such as themes, showcase sites, blog posts, plugins etc.
- It adds a
rel="nofollow ugc"attribute for this kind of content. - The main motivation here is to disincentivise people from creating or adding content/sites only for SEO back-linking.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@7.4.10
Patch Changes
-
#18621
8a61493Thanks @marcalexiei! - Fixes the dev toolbar's audit freezing an image's CSS animations in Safari, by reading the image's size from the request that loaded it instead of fetching it again -
#18691
f787792Thanks @ematipico! - Improves startup time ofastrocommands by loading SVGO only whensvgoOptimizer()optimizes an SVG, instead of wheneverastro/configis imported -
#18678
ea63d76Thanks @astro-factory! - Fixes duplicate CSS loading for hydrated islands that share modules or are imported through a path alias. The client build no longer emits and preloads stylesheets that are already linked on the page by the server build. -
Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/markdown-satteri@0.4.8
- @astrojs/vite-plugin-astro@0.1.1
@astrojs/cloudflare@14.4.7
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/underscore-redirects@1.0.4
@astrojs/markdoc@2.1.4
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/mdx@8.1.4
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/markdown-satteri@0.4.8
@astrojs/netlify@8.2.13
Patch Changes
- #18680
4f8e19aThanks @florian-lefebvre! - Prevents server function traces from including the entire project when a dependency uses paths the tracer cannot resolve. - Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/underscore-redirects@1.0.4
@astrojs/node@11.1.12
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/preact@6.1.4
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/preact-renderer@0.1.1
@astrojs/react@7.1.7
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/react-renderer@0.1.1
@astrojs/solid-js@7.1.4
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/solid-js-renderer@0.1.0
@astrojs/svelte@9.1.4
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/svelte-renderer@0.1.0
@astrojs/vercel@11.0.21
Patch Changes
- #18680
4f8e19aThanks @florian-lefebvre! - Prevents server function traces from including the entire project when a dependency uses paths the tracer cannot resolve. - Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/vue@7.1.4
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
- @astrojs/vue-renderer@0.1.0
@astrojs/internal-helpers@0.13.2
Patch Changes
- #18695
57137edThanks @matthewp! - Adds the@astrojs/internal-helpers/rendererexport used by@astrojs/react,@astrojs/preact,@astrojs/solid-js,@astrojs/svelteand@astrojs/vue, which fail to load without it
@astrojs/markdown-remark@7.3.7
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/markdown-satteri@0.4.8
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/preact-renderer@0.1.1
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/react-renderer@0.1.1
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2
@astrojs/vite-plugin-astro@0.1.1
Patch Changes
- Updated dependencies [
57137ed]:- @astrojs/internal-helpers@0.13.2


Changes
- Errors thrown after a page has started streaming are now logged exactly once through the configured pipeline logger (e.g.
logHandlers.json()), as a single structured record withlevel: "error"— the same as errors thrown before the first byte. Previously they were printed bywriteResponseviaconsole.erroras multi-line plain text, bypassing any custom logger entirely; adapters that hand the body to their runtime untouched (Bun, Deno) logged nothing at all. SSRResultnow carries an optional logger set fromFetchStateincreateResult(). Both streaming renderers (renderStreamToAsyncIterableandrenderStreamToStream) log the error once and stamp it withSymbol.for('astro.streamErrorLogged').writeResponseskips only stamped errors so that errors from an endpoint's ownReadableStreamare still printed as before.recordServerError()in the dev server respects the same marker and skips itslogger.errorcall for already-logged errors, preventing a duplicate record inastro dev.
Testing
packages/astro/test/units/render/streaming.test.ts— new unit tests covering the mid-stream error path for bothAsyncIterableandReadableStreambodies, asserting a single logger call with the correct level and noconsole.erroroutput.packages/astro/test/units/app/node.test.ts— updated to assert thatwriteResponsestill prints errors from endpoint streams that were never touched by the renderer.packages/astro/test/streaming-error-logger.test.ts— new dev-server integration test asserting that a mid-stream page error produces exactly one error record inastro dev.
Docs
No docs update needed — this is a bug fix that restores expected logger behaviour with no API changes.
Closes #18625

Changes
dist/.vite/license.md(and its equivalents in server/client output dirs) is now preserved afterastro buildwhenvite.build.licenseis set. Previously,removeViteManifestDirectories()removed the entire.vite/folder recursively, silently deleting the licence file Vite writes there.- The cleanup now deletes only
.vite/manifest.jsondirectly, then removes the.vite/directory only if it is empty afterwards. Files Vite writes alongside the manifest (such asbuild.licenseoutput) are left untouched.
Testing
- Added
packages/astro/test/units/build/remove-vite-manifest-directories.test.ts, covering: manifest-only directories are removed, non-empty directories with extra files are kept after manifest deletion, and builds without a manifest leave nothing behind.
Docs
- No docs update needed; this restores behaviour that already matches Vite's own output and requires no new user-facing config.
Closes #18685

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/preact-renderer@0.1.0
Minor Changes
Patch Changes
@astrojs/react-renderer@0.1.0
Minor Changes
Patch Changes
@astrojs/solid-js-renderer@0.1.0
Minor Changes
Patch Changes
@astrojs/svelte-renderer@0.1.0
Minor Changes
Patch Changes
@astrojs/vue-renderer@0.1.0
Minor Changes
Patch Changes
@astrojs/runtime@0.1.0
Minor Changes
-
#18611
f98e8a8Thanks @matthewp! - Adds standalone rendering:astro()compiles.astrofiles in a plain Vite project, andrenderToString()/renderToResponse()from@astrojs/runtimerender a component tree with its stylesheets, scripts and framework islands in dev and in builds -
#18611
f98e8a8Thanks @matthewp! - Adds declarative renderer fields: anAstroRenderercan carryoptions(passed to its server entrypoint asthis.options),optimizeDeps,dedupe,noExternal(a list, or a function of the project root for lists found by crawling dependencies), a dev-onlydevHeadScriptand anappEntrypointthat its entrypoints import, whichastro()applies, so a renderer is plain data next to the framework's own Vite plugin
Patch Changes
-
#18630
c904827Thanks @astro-factory! - Fixes bundled scripts and hydrated islands being blocked whensecurity.csp.scriptDirective.strictDynamicis enabled. Astro now adds the hash of every bundled script toscript-srcand renders an import map with theirintegrityin the<head>. -
#18688
1999c84Thanks @astro-factory! - Fixes errors thrown after a page has started streaming bypassing the configuredlogger. They are now reported once through it, as oneerrorrecord, in both production andastro dev
@astrojs/vite-plugin-astro@0.1.0
Minor Changes
-
#18611
f98e8a8Thanks @matthewp! - Adds standalone rendering:astro()compiles.astrofiles in a plain Vite project, andrenderToString()/renderToResponse()from@astrojs/runtimerender a component tree with its stylesheets, scripts and framework islands in dev and in builds -
#18611
f98e8a8Thanks @matthewp! - Adds declarative renderer fields: anAstroRenderercan carryoptions(passed to its server entrypoint asthis.options),optimizeDeps,dedupe,noExternal(a list, or a function of the project root for lists found by crawling dependencies), a dev-onlydevHeadScriptand anappEntrypointthat its entrypoints import, whichastro()applies, so a renderer is plain data next to the framework's own Vite plugin
Patch Changes
astro@7.4.9
Patch Changes
-
#18681
bf1828bThanks @astro-factory! - Fixes static builds skipping or failing on pages whosegetStaticPaths()params contain characters like%or\, and warns when a prerendered page is skipped because it returned an empty error response -
#18630
c904827Thanks @astro-factory! - Fixes bundled scripts and hydrated islands being blocked whensecurity.csp.scriptDirective.strictDynamicis enabled. Astro now adds the hash of every bundled script toscript-srcand renders an import map with theirintegrityin the<head>. -
#18611
f98e8a8Thanks @matthewp! - Fixes bundling of a<script src>that uses a root-relative path to a project file outsidesrc/, such as/lib/analytics.ts. The error asking foris:inlineis now shown only when the path points to a file inpublic/. -
#18688
1999c84Thanks @astro-factory! - Fixes errors thrown after a page has started streaming bypassing the configuredlogger. They are now reported once through it, as oneerrorrecord, in both production andastro dev -
Updated dependencies [
c904827,5083c65,1999c84,5083c65,f98e8a8,f98e8a8]:- @astrojs/runtime@0.1.0
- @astrojs/vite-plugin-astro@0.1.0
@astrojs/preact@6.1.3
Patch Changes
- Updated dependencies [
ff1cf65]:- @astrojs/preact-renderer@0.1.0
@astrojs/react@7.1.6
Patch Changes
- Updated dependencies [
ff1cf65]:- @astrojs/react-renderer@0.1.0
@astrojs/solid-js@7.1.3
Patch Changes
- Updated dependencies [
ff1cf65]:- @astrojs/solid-js-renderer@0.1.0
@astrojs/svelte@9.1.3
Patch Changes
- Updated dependencies [
ff1cf65]:- @astrojs/svelte-renderer@0.1.0
@astrojs/vue@7.1.3
Patch Changes
- Updated dependencies [
ff1cf65]:- @astrojs/vue-renderer@0.1.0
astro-vscode@2.17.4
Patch Changes
- #18692
ad77e9eThanks @Princesseuh! - Republishes the extension to the VS Code Marketplace and Open VSX, which were missed in the previous release

Changes
- Fixes the broken
pnpm-lock.yamlonmain(ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY: no entry for 'rolldown@1.3.0'), which failspnpm installin every CI job. - #18679 pinned
rolldownto~1.2.16and removed the 1.3.0 entries from the lockfile, while #18610 resolved@astrojs/vite-plugin-astro'srolldownto 1.3.0. The two lockfile changes merged cleanly as text but left a reference to a removed entry. - Pins
rolldownin@astrojs/vite-plugin-astroto~1.2.16, like the rest of the repo, and regenerates the lockfile.
Testing
pnpm install --frozen-lockfilepasses.
Docs
- No docs update needed.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| @hono/node-server | 2.0.4 → 2.1.6 |
@hono/node-server: serveStatic decodes the request path a second time, leading to bypass of middleware on static paths
CVE-2026-118663 / GHSA-rmxm-3fg6-px4f
More information
Details
Summary
serveStatic decodes the request path a second time after Hono has already decoded it for routing. A crafted request can be routed as one path and served as another, so middleware mounted on a static prefix does not run for a file under that prefix.
Details
Hono decodes the request path once before routing. serveStatic decoded it again before resolving the file. With a malformed percent-encoded sequence, the first decode leaves part of the path encoded, the router matches the encoded form, and the second decode resolves the real directory. The file is still resolved inside the configured root; this is not a traversal outside it.
Impact
An unauthenticated attacker may reach static files without the middleware on their prefix running, for example an authentication check. This affects applications that mount middleware on part of the directory served by serveStatic. Applications that serve only public files are not affected.
Severity
- CVSS Score: 5.3 / 10 (Medium)
- Vector String:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
References
- https://github.com/honojs/node-server/security/advisories/GHSA-rmxm-3fg6-px4f
- https://github.com/honojs/node-server/commit/982179278529d5673812116b042829f27794966f
- https://github.com/honojs/node-server/releases/tag/v2.1.3
- https://github.com/advisories/GHSA-rmxm-3fg6-px4f
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
@hono/node-server: Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy
CVE-2026-126210 / GHSA-jpvv-r467-5p4w
More information
Details
Summary
@hono/node-server passes the raw request-target to the WHATWG URL parser, which treats a backslash in the path as / and then resolves .. segments. A request for /admin\secret or /public\..\admin/secret reaches the application as /admin/secret. A reverse proxy that follows RFC 3986 forwards the backslash unchanged and applies its path-based rules to the original path, so the request reaches a route the proxy is meant to block.
Details
A raw backslash is not allowed in a request-target (RFC 3986, RFC 9112 Section 3.2.1), and RFC 9112 Section 3.2 says a recipient should reject such a request rather than correct it. Proxies such as nginx on Linux, HAProxy and Envoy keep the backslash as an ordinary character, so they and the application see different paths.
The fix responds with 400 Bad Request to a request whose path contains a raw backslash, for HTTP/1.1, HTTP/2, absolute-form request-targets and WebSocket upgrades. A percent-encoded backslash and a backslash in the query string are still accepted.
Impact
An unauthenticated client can reach a route that a reverse proxy, load balancer or WAF in front of the application blocks by path.
This affects applications served by @hono/node-server behind a front component that makes path-based decisions and forwards a backslash unchanged. Access control inside the Hono application, such as middleware on /admin/*, runs on the rewritten path and is not affected.
Severity
- CVSS Score: 5.3 / 10 (Medium)
- Vector String:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
References
- https://github.com/honojs/node-server/security/advisories/GHSA-jpvv-r467-5p4w
- https://github.com/honojs/node-server/commit/3868998a805ae79216535ad3986c1e7228dee313
- https://github.com/honojs/node-server/commit/fb97395ec36af66567c76976e741110b02804d1c
- https://github.com/honojs/node-server/releases/tag/v1.19.18
- https://github.com/honojs/node-server/releases/tag/v2.1.6
- https://github.com/advisories/GHSA-jpvv-r467-5p4w
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
honojs/node-server (@hono/node-server)
v2.1.6
Security fixes
This release includes fixes for the following security issues:
Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy
Affects: all requests. The raw request-target was passed to the WHATWG URL parser, which treats a backslash in the path as / and resolves .. segments, so /admin\secret reached the application as /admin/secret. A reverse proxy that forwards the backslash unchanged applied its path-based rules to the original path. GHSA-jpvv-r467-5p4w
A request whose path contains a raw backslash is now rejected with 400 Bad Request, for HTTP/1.1, HTTP/2 and WebSocket upgrades. A percent-encoded backslash (%5C) and a backslash in the query string are still accepted.
WebSocket upgrade request-target starting with // replaces the host in c.req.url, bypassing Origin checks
Affects: upgradeWebSocket. The URL of an upgrade request was built by resolving the request-target against the Host header, so a request-target such as //attacker.example/ws set the host of c.req.url to a client-chosen value while routing still saw /ws. An application that compared Origin with the origin of c.req.url could be bypassed by a page on another site. GHSA-7v5p-43qr-wch5
The host of upgrade requests now comes from the Host header, as for ordinary requests.
Unhandled ECONNRESET on the socket during an asynchronous WebSocket upgrade crashes the process
Affects: upgradeWebSocket. While the application handled an upgrade request, the socket had no error listener. A client that reset the connection during asynchronous middleware caused an unhandled 'error' event and terminated the process. GHSA-qv5m-9pm6-hqp3
Error and close events on the socket are now handled while the application runs, and a pending upgrade is released when the socket closes.
The backslash fix also ships in @hono/node-server v1.19.18. Users of upgradeWebSocket are encouraged to upgrade to this version.
v2.1.5
What's Changed
- fix(listener): abort the request signal when an HTTP/2 client resets the stream by @affanmomin in #404
- fix(serve-static): only serve GET and HEAD requests by @usualoma in #405
New Contributors
- @affanmomin made their first contribution in #404
Full Changelog: honojs/node-server@v2.1.4...v2.1.5
v2.1.4
What's Changed
- chore: allow hono v5 as a peer dependency by @yusukebe in #406
Full Changelog: honojs/node-server@v2.1.3...v2.1.4
v2.1.3
Security fixes
serveStatic decodes the request path a second time, leading to bypass of middleware on static paths
Affects: @hono/node-server/serve-static. Fixes serveStatic decoding an already-decoded path, where a crafted request could be routed as one path and served as another, skipping middleware mounted on a static prefix. GHSA-rmxm-3fg6-px4f
serveStatic now rejects request paths that still contain % after decoding. To serve files whose names contain a literal %, set allowPercentInPath: true.
The same fix ships in hono v4.13.11.
v2.1.2
What's Changed
- ci: add autofix.ci by @yusukebe in #392
- fix: type error in early hints and add typecheck to CI by @BlankParticle in #390
- chore: add better benchmarks by @BlankParticle in #391
- docs(readme): update the benchmark by @yusukebe in #394
- test(request): accept asynchronous body read errors by @usualoma in #403
- fix(listener): avoid mutating response headers when setting Content-Length by @usualoma in #402
Full Changelog: honojs/node-server@v2.1.1...v2.1.2
v2.1.1
What's Changed
- perf: lazily materialize request headers by @BlankParticle in #389
Full Changelog: honojs/node-server@v2.1.0...v2.1.1
v2.1.0
What's Changed
- feat: add Early Hints (HTTP 103) middleware by @bilal-azam in #378
- fix(listener): avoid uncaught error when force-closing a non-standard socket by @mohamedramadan14 in #383
New Contributors
- @bilal-azam made their first contribution in #378
- @mohamedramadan14 made their first contribution in #383
Full Changelog: honojs/node-server@v2.0.12...v2.1.0
v2.0.12
What's Changed
- test: replace supertest by @BlankParticle in #379
- fix(response): copy headers when init is a foreign Response by @yusukebe in #382
Full Changelog: honojs/node-server@v2.0.11...v2.0.12
v2.0.11
What's Changed
- test: use a custom helper for path traversal tests by @BlankParticle in #377
- perf(request): fast-path QUERY methods by @usualoma in #376
- perf(request): fast-path PATCH method by @yusukebe in #380
Full Changelog: honojs/node-server@v2.0.10...v2.0.11
v2.0.10
Security fixes
This release includes a fix for the following security issue:
Unauthenticated memory-leak DoS via aborted WebSocket handshake
Affects: upgradeWebSocket. A WebSocket upgrade request with a missing or malformed Sec-WebSocket-Key header leaked the request's IncomingMessage and left a promise pending, even though no connection was established. Since the route is reachable pre-handshake without authentication, an attacker could flood it to gradually exhaust memory. GHSA-9mqv-5hh9-4cgg
Users of upgradeWebSocket are encouraged to upgrade to this version.
v2.0.9
What's Changed
- fix(websocket): polyfill missing ErrorEvent global by @otnc in #371
- fix(serve-static): correct Range header parsing edge cases by @otnc in #372
- fix: recover complete request bodies after client disconnect by @usualoma in #375
New Contributors
Full Changelog: honojs/node-server@v2.0.8...v2.0.9
v2.0.8
What's Changed
- ci(release): add
--no-git-checksoption forpnpm stage publishby @yusukebe in #369
Full Changelog: honojs/node-server@v2.0.7...v2.0.8
v2.0.6
What's Changed
- ci: publish to npm from CI with OIDC trusted publishing and bump
npby @yusukebe in #361 - ci: use npm Staged publishing by @yusukebe in #364
- fix: preserve status and statusText when cloning a Response with liveheaders by @usualoma in #363
Full Changelog: honojs/node-server@v2.0.5...v2.0.6
v2.0.5
Security Fix
Fixed a security issue in Serve Static Middleware where prefix-mounted middleware could be bypassed on Windows. This only affects applications running on Windows that use Serve Static Middleware. Affected users are encouraged to upgrade to this version.
See GHSA-frvp-7c67-39w9 for details.
Configuration
📅 Schedule: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

Changes
getStaticPaths()routes whose params contain a literal%(e.g.50%-off) or other URI-special characters are now correctly written todist/during a static build. Previously,getUrlForPathpassed the raw decoded pathname tonew URL()without encoding it first. Since 6.0 the render pipeline decodesrequest.urlto recover the pathname, so a bare%causeddecodeURIto throw, returning an empty400that silently dropped the file.getUrlForPath(packages/astro/src/core/build/common.ts) now callsencodeURI(pathname)before constructing the request URL. This keeps the parallel prerenderer's static-path map keys and the request URLs produced bygenerate.tsin sync.renderPathnow emits a warning that includes the HTTP status and pathname when an error response with no body is skipped, making similar regressions immediately visible.
Testing
- New unit tests in
packages/astro/test/units/build/common.test.tscovergetUrlForPathfor paths containing%,\, and pre-escaped sequences (e.g.%23), asserting that round-tripping the resulting URL's pathname throughvalidateAndDecodePathnamereturns the original path. - New build-level test
packages/astro/test/static-paths-special-chars.test.tsexercises agetStaticPathsfixture with params50%-off,café,tag#1, anda\b, asserting each is written to the expecteddist/path with the correctAstro.paramsvalue.
Docs
No docs update needed — this restores previously working behavior with no API or config changes.
Closes #18659
Description
- What does this PR change? A few external links in the translated docs go to pages that don't exist:
https://astro.build/it/(it/getting-started) andhttps://astro.build/ru/(ru/guides/authoring-content, twice). astro.build has no localized home pages, so these now go tohttps://astro.build/like the English pages.https://docs.astro.build/pt-pt/concepts/islands/andhttps://docs.astro.build/pt/reference/cli-reference/#astro-devin the pt-pt pages. The Astro docs only havept-br, which the other pt-pt pages already link to.https://git-scm.com/docs/git-clone/dein de/reference/configuration. git-scm.com has no German translation of git-clone, so it now links to the English page with its current--depthanchor.
- I checked each old URL (404) and new URL (200) with curl, and the
astro-devanchor exists on the pt-br page. - Nothing visual.

Changes
Followup to another NFT fix I contributed last week
- Ignore project-wide NFT globs even when the project root matches the trace base, preventing Vercel and Netlify functions from including entire repositories.
- Keep package-scoped globs traceable and preserve the workspace trace base.
- Made with AI
Testing
- Add a Vercel unit test for filtering project-wide globs while retaining package-scoped globs.
- The Vercel and Netlify monorepo trace tests cover server chunks, runtime
process.cwd()assets, and unrelated workspace files.
Docs
Changeset

Changes
- Removes direct
@emnapi/runtimepins from the language-tools packages so they can rely on@astrojs/astro2tsxto install the WASM runtime. - compiler-rs#219 moves
@emnapi/runtimeinto@astrojs/astro2tsxruntime dependencies - Pins rolldown to a compatible version
Testing
N/A
Docs
Removes an unreleased changeset
AI was used to prepare this PR description.

Changes
- Hydrated island components imported through a tsconfig path alias are now resolved to their absolute module id (via
this.resolve()) before being stored inpagesByHydratedComponent, matching howclient:onlycomponents are handled. Previously the raw alias specifier was used, soshouldDeleteCSSChunknever matched it and the client CSS was never removed. - The CSS build plugin now also drops client CSS for chunks that island entry chunks import statically (non-dynamic imports only), when all of that chunk's CSS modules are already in the SSR build and no
client:onlycomponent,<script>, or renderer has an exclusive path to the chunk. This covers the shared-module case (e.g. two islands sharingCard.tsx → Card.css) where Rollup/Rolldown splits the shared code into its own chunk whose CSS was always kept and injected by Vite's preload helper at runtime.
Testing
- Extends the
css-deduplicationfixture and its test suite (packages/astro/test/css-deduplication.test.ts) with cases for alias-imported islands and islands that share a CSS-importing module, asserting that the client copies of the duplicate CSS files are absent from the build output and from__vite__mapDeps.
Docs
- No docs update needed; this is an internal build-pipeline deduplication fix with no user-facing API changes.
Closes #18677

This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| mcr.microsoft.com/devcontainers/javascript-node | final | major | 4-22 → 5-22 |
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| autocannon | ^8.0.0 → ^9.0.0 |
Release Notes
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| withastro/automation (changelog) | workflow | digest | 497c926 → 4105de6 |
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| semgrep/semgrep | container | digest | 40579a2 → fb59331 |
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

Changes
- When
astro checkloads@astrojs/check, a barecatch {}previously swallowed bothrequire.resolve()failures (package not installed) andimport()failures (package installed but broken). Both cases produced the same "dependency is missing" prompt, hiding the real crash. Now only therequire.resolve()call is wrapped in the catch;import()runs outside it, so load-time errors likeTypeError: this.bridge.setLastError is not a functionpropagate to the CLI's normal error handler with a full stack trace. - This surfaces the true failure when a transitive dependency version mismatch (e.g.
@emnapi/core@1.11.3paired with@emnapi/runtime@2.0.0-beta.2) causes the checker to crash on import, making the problem diagnosable without workarounds.
Testing
- Updated
packages/astro/test/units/cli/install-package.test.tsto cover the case whererequire.resolve()succeeds (package is present) butimport()throws, verifying the error is now rethrown rather than treated as a missing package.
Docs
- No docs update needed; this is a CLI error-reporting fix with no user-facing API change.
Closes #18653

Changes
macos-14 has been retired since November 2nd, 2026: https://github.blog/changelog/2026-10-01-github-actions-macos-14-runner-image-retirement/
Our current CI is red because of the error The configuration 'macos-14-arm64-us-default' is not supported:
This PR updates the macOS runner to macos-15.
Testing
CI should be green.
Docs
N/A

Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
Release Notes
babel/babel (@babel/core)
v8.1.0
🚀 New Feature
babel-helper-module-transforms,babel-helper-transform-fixture-test-runner,babel-helpers,babel-plugin-proposal-bytes-modules,babel-plugin-proposal-filtered-namespaces,babel-plugin-proposal-import-wasm-source,babel-plugin-proposal-text-modules,babel-plugin-transform-dynamic-import,babel-plugin-transform-json-modules,babel-runtime-corejs3,babel-runtime,babel-standalone- #18316 Add transform support for filtered namespaces (@nicolo-ribaudo)
babel-generator,babel-helper-import-to-platform-api,babel-helper-module-transforms,babel-parser,babel-plugin-transform-export-namespace-from,babel-plugin-transform-json-modules,babel-plugin-transform-modules-amd,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-modules-umd,babel-traverse,babel-types- #18311 Add parsing&printing support for filtered namespaces (@nicolo-ribaudo)
- Other
babel-helper-import-to-platform-api,babel-helper-transform-fixture-test-runner,babel-helpers,babel-plugin-proposal-bytes-modules,babel-plugin-proposal-import-wasm-source,babel-plugin-proposal-text-modules,babel-plugin-transform-json-modules,babel-runtime-corejs3,babel-runtime- #17817 Add support for
type: bytesandtype: textimports (@nicolo-ribaudo)
- #17817 Add support for
babel-generator,babel-parser,babel-traverse,babel-typesbabel-generator,babel-parser,babel-typesbabel-generator,babel-helper-module-transforms,babel-parser,babel-plugin-transform-export-namespace-from,babel-plugin-transform-modules-amd,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-modules-umd,babel-types- #18310 Add parsing&printing support for
export defer(@nicolo-ribaudo)
- #18310 Add parsing&printing support for
babel-cli,babel-core,babel-generator,babel-helper-transform-fixture-test-runner- #18006 Add experimental support for range mappings in source maps (@nicolo-ribaudo)
babel-corebabel-core,babel-plugin-transform-classes- #18387 Add
noUninitializedThisassumption (@nicolo-ribaudo) - #18386 Add
noClassPrototypeAssignandnoConstructorPrimitiveReturn(@nicolo-ribaudo)
- #18387 Add
🐛 Bug Fix
babel-parserbabel-helper-skip-transparent-expression-wrappers,babel-plugin-transform-optional-chaining- #18477 Fix optional call losing the receiver through a TS instantiation expression (@Kjubikstronk)
🔬 Output optimization
cloudflare/workers-sdk (@cloudflare/vitest-plugin)
v1.6.0
Minor Changes
-
#16186
f1d81a2Thanks @leostera! - Support local Artifacts across Wrangler, Vite, and Workers VitestSet
remote: falseon an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omittedremotecontinues to use the deployed resource, with a warning that changes affect real repositories;remote: trueexplicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite'sremoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator whenremoteis omitted, so tests do not change real repositories by accident; setremote: trueto test against the deployed resource. Local development does not require Cloudflare credentials, but does require Git 2.32 or newer on the host.In Miniflare's own options, Artifacts bindings route like every other binding: only
dev.remote: truewith a remote proxy connection uses the deployed resource. Wrangler and Vite resolve the deployed-by-default rule, and Workers Vitest its local default, before passing options to Miniflare.
Patch Changes
-
#16700
dc35efbThanks @cjol! - Bump bundledbrace-expansionto pick up security fixesThese packages bundle
brace-expansion(a dependency ofminimatch), and the bundled versions were affected by published advisories. The bundles now includebrace-expansion2.1.7 (from 2.0.1) and 5.0.12 (from 5.0.5). Normal glob patterns expand as before; only the pathological patterns targeted by the advisories are handled differently. -
#16700
dc35efbThanks @cjol! - Bump bundleddevaluefrom 5.6.3 to 5.9.3 to pick up security fixesdevalueis bundled into these packages, which use it to serialise values between Node.js and workerd. Version 5.6.3 is affected by several published advisories, and 5.9.3 includes their fixes. Serialisation behaviour does not change. -
#16700
dc35efbThanks @cjol! - Bump bundledminimatchfrom 5.1.6 to 5.1.9 to pick up security fixesThese packages bundle
minimatch, and 5.1.6 is affected by published ReDoS advisories. Version 5.1.9 includes the fixes. 5.1.8 is skipped because it broke recursive**matching, which D1'smigrations_patternrelies on. -
#16695
b2061f4Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-04Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
Updated dependencies [
dc35efb,dc35efb,dc35efb,dc35efb,dc35efb,dc35efb,dc35efb,b8387a5,fa3edb3,4cde694,b2061f4,b2061f4,f1d81a2,4bb491b,36e64f2,92c4b97]:- wrangler@4.158.0
- miniflare@5.20261104.0-beta
v1.5.1
Patch Changes
-
#16670
b14b9dcThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-03Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#16609
da26b7fThanks @gpanders! - Fix tests failing to start withresolve.preserveSymlinksin isolatednode_moduleslayoutsWith
resolve.preserveSymlinks: truein a pnpm project, tests failed to start withNo such module ".../node_modules/vitest/dist/chai", because a package's own dependencies are linked only next to its real path. Packages linked from a store insidenode_modulesnow load from their real paths, and other files keep their symlinked paths. -
Updated dependencies [
b14b9dc,44d1ee4,b14b9dc,d2eda1c,2750917,34f34b3]:- miniflare@5.20261103.0-beta
- wrangler@4.157.0
v1.5.0
Minor Changes
-
#16424
1598fd3Thanks @edmundhung! - Promoteexperimental.newConfigto a stableconfigoptionThe experimental
experimental.newConfigoption is now the stableconfigoption. Passconfig: truetocloudflareTest()to load your Worker's bindings, entrypoint and compatibility settings fromcloudflare.config.tsin the project root, or pass the path of acloudflare.config.tselsewhere:cloudflareTest({ config: true }); cloudflareTest({ config: "./worker/cloudflare.config.ts" });
configcan't be combined withwrangler.miniflareoptions are merged over the Worker fromcloudflare.config.ts, withminiflarevalues taking precedence. Config functions receive Vitest's mode asctx.mode, which defaults totestand can be changed with--mode.If you're moving from
experimental.newConfig, secrets are now read from Vite'senvDirinstead of the directory containingcloudflare.config.ts, and remote bindings authenticate withcfinstead of Wrangler.
Patch Changes
-
#16642
d38cb02Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-02Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
#16623
51bbf8bThanks @petebacondarwin! - Deprecate shared tooling helper exports from MiniflareMiniflare continues to export
getNodeCompat,NodeJSCompatMode, andgetFreshSourceMapSupportfor compatibility. These exports are deprecated and now use the implementations in@cloudflare/workers-utils. Add a dependency on that package and replace the Miniflare imports with:import { getNodeCompat, type NodeJSCompatMode, } from "@cloudflare/workers-utils/node-compat"; import { getFreshSourceMapSupport } from "@cloudflare/workers-utils/sourcemap";
Wrangler and the Cloudflare Vite and Vitest plugins now use the shared helpers directly. The helpers retain their behavior and can be imported without loading the Workers runtime.
The deprecated Miniflare exports will be removed in a later release, allowing downstream tools such as cf to migrate and release independently first.
-
Updated dependencies [
d38cb02,d38cb02,51bbf8b,e5b1798]:- miniflare@5.20261102.0-beta
- wrangler@4.156.2
v1.4.12
Patch Changes
-
#16635
76e18a8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-01Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
-
Updated dependencies [
effe4ed,76e18a8,76e18a8,009ca6e,5740867,d174de8,aece4df,2667a9f,ed7fb41,f9dbb22]:- wrangler@4.156.1
- miniflare@5.20261101.0-beta
earendil-works/pi (@earendil-works/pi-ai)
v0.99.2
Added
- Added the lightweight
@earendil-works/pi-ai/modelsentry point for model collections and provider construction without loading TypeBox, built-in catalogs, or provider SDKs. - Added Anthropic workload identity federation from the Anthropic SDK environment variables
ANTHROPIC_FEDERATION_RULE_ID,ANTHROPIC_ORGANIZATION_ID, andANTHROPIC_IDENTITY_TOKEN_FILE(plus optionalANTHROPIC_SERVICE_ACCOUNT_IDandANTHROPIC_WORKSPACE_ID). API keys andANTHROPIC_AUTH_TOKENtake precedence (#10177, #10242 by @philfreo)
Fixed
- Fixed context overflow detection for Z.AI CN endpoint
Prompt exceeds max lengtherrors (#10208) - Fixed Anthropic requests failing when a
strict: "prefer"tool schema uses keywords Anthropic strict tool use rejects, such asminimum/maximum; such tools are now sent non-strict (#9953) - Fixed provider retries firing immediately when a
Retry-Afterheader contains an unparseable date; they now use exponential backoff (#9571)
v0.99.1
Added
- Added GPT-6.1 Sol (
gpt-6.1-sol) to the OpenAI, Azure OpenAI Responses, and OpenAI Codex providers.
v0.99.0
Breaking Changes
- Unified image models into the regular
Provider/Modelssurface. The separateImagesModelscollection is removed:createImagesModels(),createImagesProvider(),ImagesProvider,openrouterImagesProvider(),builtinImagesProviders(), andbuiltinImagesModels()are gone. UsebuiltinModels(),models.getModelOfType("image", ...),models.generateImages(), andcreateProvider({ models, images })instead. Existing unqualified reads remain chat-only. - Image models are now
ImageModelwith a requiredtype: "image"and shareBaseModelwith chat models. The old plural image type names (ImagesModel,ImagesApi,KnownImagesApi,KnownImagesProvider, andImagesProviderId) are removed.generateImages()accepts only image models. Output modalities (output) remain on image models only. - Generated model data schema is now version 6: every entry carries
type, operation-specific catalogs include chat, image, and classifier models, and one upstream ID may have separate entries per type. OpenRouter image models live in theopenrouter-imagesapi group ofopenrouter.json;image-models.generated.tsandscripts/generate-image-models.tsare removed. Runnpm run hydrate:model-data.
Added
- Added
Models.generateImages()with provider-resolved auth,Provider.generateImages?, andcreateProvider({ images })keyed bymodel.api.createProvider()modelsandfetchModelsaccept models of every type, andapiis optional whenimagesorclassifiersis given. - Added an optional model
type("chat","image", or"classifier"). Chat models may omit it, so existing chat models, providers, and stores keep working unchanged. Narrow mixed lists with the newisModelType()guard or read the effective type withgetModelType(). - Added
getModelsOfType(),getModelOfType(),getAvailableOfType(),getAllModels(), andgetAllAvailable()onModels; optionalProvider.getAllModels()andProvider.filterAllModels(); corresponding generated-catalog accessors; and theAnyModelandModelTypeMaptypes.hasApi(),calculateCost(), andmodelsAreEqual()acceptAnyModel. - Added support for models of every type in
ModelsStoreEntry.models. Stored and fetched models of unknown types are dropped instead of failing a refresh. - Added classifier models and
Models.classify()with a provider-neutral JEV-stylechoice/score/boolcontract. The built-in TypeSafe provider exposes models.dev'sjev-latestthrough the System One API and translates publicboolquestions to TypeSafe'snoulwire format. - Added Jev classifier models on OpenRouter (
typesafe/jev-1.13,~typesafe/jev-latest) through its TypeSafe-compatible System One endpoint, and on Cloudflare Workers AI (typesafe/jev) through the newcloudflare-workers-ai-system-oneclassifier API. - Added Jev classifier models on Vercel AI Gateway (
typesafe-ai/jev, generated from its evaluation model catalog) and OpenCode Zen (jev-1.13,jev-1.13-free) through their TypeSafe-compatible System One endpoints. - Added
usagetoClassifierResult: System One classifications report token counts, priced from the model catalog like chat usage. - Added a runtime chat-model check to the
Modelsstream entry points so non-chat models fail with a clearModelsErrorinstead of a missing-api stream error. - Added array-based
models.all.jsonandproviders/{id}.all.jsonvariants to the generated and published JSON catalog, allowing the same upstream ID once per model type; the existing keyedmodels.jsonandproviders/{id}.jsonstay chat-only for released clients. - Added
onProviderStreamEventto observe parsed provider stream events before normalization, including provider-specific fields not retained in assistant messages (#9784, #9901 by @davidbrai). - Added Claude Sonnet 5.5 to the built-in Anthropic model catalog with adaptive thinking, mid-conversation effort, 1M context, and official pricing metadata.
- Added Sign in with ChatGPT to the
openaiprovider: an OAuth login that uses a ChatGPT subscription with the OpenAI API.Models.login()acceptsLoginOptionswithgetDeviceId(), which supplies a stable installation ID to login flows that need one. Subscription usage-limit errors are not retried and link to the ChatGPT usage page; temporary usage errors are retried. - Added the
llama-cpp-classifyclassifier API, which answers classifier questions from llama-server's next-token probabilities for single-token answer labels. - Added optional
AssistantMessage.thinkingLevel, which records the thinking level the agent loop requested for a response.
Changed
- Renamed the OpenAI Codex provider to "OpenAI Codex (legacy)"; Sign in with ChatGPT on the
openaiprovider supersedes it. - Unified the Anthropic, OpenAI Codex, OpenRout
[!IMPORTANT]
✂ PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

Changes
- Fixes
NoImageMetadatafor SVGs whose root<svg>tag ends after the first 1000 bytes, such as draw.io exports that store the diagram in thecontentattribute. Same root cause as image-size/image-size#410 (now on Codeberg: https://codeberg.org/image-size/image-size/issues/410), which #13006 was closed in favor of. - When the first 1000 bytes contain the start of an
<svgtag but not its end, the vendored SVG check scans the rest of the input once for a>outside quoted attribute values. Other files keep the fast path, and the scan takes linear time.
Testing
- Adds
test/units/assets/image-size-svg.test.ts, covering an SVG whose root tag ends after the first kilobyte, a>inside a quoted attribute value after the first kilobyte, a long input whose root tag is never closed, and input that has an<svg>tag only after the first kilobyte (still rejected).
Docs
- No docs update needed, because this is a bug fix with no API or configuration change.

Changes
- Removes the
server-destroydependency - no behavior change.
- A small, safe cleanup
Testing
- Added a unit test using AI
Docs
N/A, internal refactor.

All three examples develop against astro ^7.4.7 but declare peer ranges that stop at 6:
examples/integration/package.json peer ^4.0.0 dev ^7.4.7
examples/component/package.json peer ^5.0.0 || ^6.0.0 dev ^7.4.7
examples/toolbar-app/package.json peer ^4.6.1 dev ^7.4.7
create-astro scaffolds these straight into a user's project, so the mismatch is not internal. Reproduced with the published create-astro@5.3.1 against the live examples/* branches — scaffold, npm pack, install into a project with astro ^7.4.7:
npm error ERESOLVE could not resolve
npm error peer astro@"^4.0.0" from integration-app@0.0.1
npm exits 1 for all three (integration, component, toolbar-app).
Why it keeps happening
The v7 bump (#16488) raised devDependencies.astro in these three files and left every peer block untouched. The v6 bump (#14383) had widened component's peer the same way. So the peer range has been lagging the dev dependency by exactly one major, twice.
Change
Three lines: each peer range gains the missing majors up to 7.
integration ^4.0.0 -> ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0
component ^5.0.0 || ^6.0.0 -> ^5.0.0 || ^6.0.0 || ^7.0.0
toolbar-app ^4.6.1 -> ^4.6.1 || ^5.0.0 || ^6.0.0 || ^7.0.0I kept the older majors rather than replacing them, so existing consumers stay in range — a package released from these examples should probably drop the ones it no longer supports, but that is your call, not this fix's.
If the next major bump adds a step that updates the peer block alongside the dev dependency, this stops recurring. Happy to be told to do that differently.

Changes
This PR mirrors the upstream change at vitejs/vite-plugin-react#1540
Now the range of the peer dependency oxc-transform-react allows multiple different minor versions like 0.150.0, 0.151.0, 0.152.0, etc.
Testing
CI should just be green.
Docs
A changeset file has been added to trigger a release.

Changes
- With Schibsted Grotesk from Fontsource configured as
weights: ['400 700'],<Font cssVariable="--font-schibsted-grotesk" preload={[{ weight: '400 700', subset: 'latin' }]} />rendered no preload links. Fontsource resolves the variable file to"400 900", andcheckWeightonly matched a requested range by exact string. - A requested weight or range now matches a file whose range contains it. A range that sticks out of the file's range (
"300 700"against"400 900") still doesn't match. I went with containment because the existingreturns variable weighttest expects a"100 900"request to skip a"500 900"file. If you'd rather have overlap I can switch it, but that test would change.
I hit this on my own site and worked around it by filtering on subset only.
Testing
New unit test returns variable weight when the preloaded weight range is inside it: range inside a range, exact range, single weight inside, tab-separated range, decimal weights, ranges partly or fully outside. It fails on main with actual: [], expected: ['foo']. With the fix, node --test --experimental-strip-types test/units/assets/fonts/*.test.ts in packages/astro after pnpm run build:ci gives 118 tests, 118 pass.
Docs
No docs change. The preload docs say "Variable weight font files will be preloaded if any weight within its range is requested" and show a single weight. This makes a requested range behave the same way when it fits inside the file.
Description
This PR updates some of our lightweight CI jobs to use ubuntu-slim.
I added a comment for each change, and I also considered:
.github/workflows/welcome-bot.yml: useszephyrproject-rtos/action-first-interactionwhich uses Docker so it's a no go..github/workflows/file-icons.yml: takes around 40s to run and would probably be compatible but it runs once a week, so the impact is minimal. It also installs some font-related dependencies relying onnode-gypthat I'm not entirely sure would work withubuntu-slimso I decided to leave it as is for now.
All other jobs either run some kind of build or CPU-heavy tasks and were left out of this change.

Closes #18656
Changes
Projects without fonts configured were still loading unifont (and with it css-tree + mdn-data) and @capsizecss/unpackon every command. The fonts plugin also ran its fullbuildStartpipeline (xxhash wasm init, storage,UnifontFontResolver.create`) with zero families in need of it.
With this change:
fontsPlugin.buildStartreturns early whensettings.config.fontsis empty, matching the existing guard inbuildEnd. Every other hook already handles the unset state (?? [],if (!fontFileById) return), so the virtual modules come out the same.CapsizeFontMetricsResolverandUnifontFontResolverare imported on demand insidebuildStart.fontProviders.*()uses the literal provider name instead ofproviders.x()._name, and loads unifont ininit(). The names already match unifont's and are pinned bytest/units/assets/fonts/providers.test.ts("references the right names").- Changeset included.
SVGO also pulls in css-tree through astro/config (#18655 / #18657), so the module count only drops fully once both land. Measured on a 400-post Markdown blog, no fonts, no SVGs, macOS arm64 and Node v26. Runs were interleaved against main (39ede5f):
main |
SVGO PR only | SVGO PR + this PR | |
|---|---|---|---|
import('astro/config'): modules / source |
905 / 6.6 MB | 634 / 5.2 MB | 496 / 4.4 MB |
astro build: modules |
1441 | 1170 | 1028 |
| css-tree / unifont / svgo modules during build | 358 | 130 | 0 |
import('astro/config') wall, median n=20 |
813 ms | 643 ms | 553 ms (−32%) |
astro build (warm) wall, median n=20 |
2916 ms | 2845 ms | 2464 ms (−16%) |
astro build (warm) CPU, median n=20 |
3030 ms | 2910 ms | 2740 ms |
This PR on its own: import('astro/config') goes from 905 to 901 modules (unifont itself only), and astro build skips the font pipeline.
fontace (via fontProviders.local()) stays eager. Making it lazy needs FontFileReader.extract to become async, and it only costs ~20 ms, so I left it out to keep this diff small.
Testing
- Fonts tests:
fonts.test.ts21,fontsource.test.ts1,incremental-build-fonts.test.ts1,test/units/assets/fonts/*117. All pass. - Full
astrosuite:test:unit3859 pass / 0 fail,test:integration1361 pass / 0 fail,test:typespasses. - The built
dist/(411 files) and.astro/types of the benchmark project are byte-identical tomain.
Docs
No user-facing behavior change, so no docs needed.
AI disclosure: Code review and benchmarks were something Claude Code (Opus 5.5) helped me with.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/starlight-docsearch@0.8.2
Patch Changes
@astrojs/starlight@0.42.11
Patch Changes
- #4332
ad19424Thanks @RaphaelFakhri! - Fixes thetwitter:sitemeta tag including a trailing slash when the configured X or Twitter social link ends with/

Changes
createRoutesListchecks for route collisions by callingdetectRouteCollisionon every pair of routes, and it copies the array withroutes.slice(index + 1)on each outer iteration. That is O(R²) for R routes.- The list is rebuilt at
astro devstartup, onbuild,sync, andpreview, and in dev on every watcheradd,unlink, andchangeundersrc/(vite-plugin-routes→rebuildRoutes). So in dev, the quadratic loop runs on every save. detectRouteCollisiononly warns in two cases: the routes have the sameroutestring, or all of their segments are semantically equal. This PR groups routes by those two keys and runs the unchangeddetectRouteCollisiononly on pairs within a group. The pairs are deduplicated and sorted by their original indices, so the same warnings are logged in the same order.- Routes within a group are still compared pairwise. That only matters when many routes share the same shape, and in that case they would all produce warnings anyway.
Median of 3, Node 24.22.1, measured with astro sync on generated projects of trivial .astro pages. Each project also has two deliberate collisions: a duplicate static route and an [a]/[b] SSR pair. "Collision loop" is the time spent in the collision check alone; "total astro sync" is the wall time of the whole command.
| routes | mode | collision loop, before → after | speedup | total astro sync, before → after |
|---|---|---|---|---|
| 1,000 | static | 8.2 → 1.9 ms | 4.3× | — |
| 1,000 | SSR (prerender = false) |
21.8 → 2.0 ms | 11× | — |
| 4,000 | static | 91.8 → 5.9 ms | 16× | 0.64 → 0.56 s |
| 4,000 | SSR | 239 → 6.6 ms | 36× | 0.79 → 0.59 s |
| 16,000 | static | 1,281 → 17.5 ms | 73× | 2.3 → 0.93 s |
| 16,000 | SSR | 3,973 → 19.7 ms | 202× | 4.9 → 1.0 s |
For a typical site with a few dozen routes, this makes no noticeable difference. It matters for sites with a thousand or more file-based pages: there, the loop is paid at startup and again on every save in dev. At 4,000 SSR routes, the loop took longer than the rest of createRoutesList combined, which includes the filesystem scan and reading every page for prerender. The warning output was identical before and after at every size, in both modes.
Testing
- Added a
createRoutesListunit test intest/units/routing/manifest.test.ts. It pins the exact warnings and their order for:- a duplicate static route (file-based plus injected)
- colliding dynamic (
[foo]/[bar]) and rest (docs/[...a]/docs/[...b]) SSR routes - same-shape routes where both or one is prerendered (no warning)
- non-colliding look-alikes (
blog/[slug]vsblog-[slug],item/[id]/editvsitem/[id]/view,[...rest])
test/units/routing/: 319 pass with this change. The new test also passes onmainwithout the change, so it pins the existing warnings and order.
Docs
No docs change. There is no change to behavior or output, only to performance.
AI disclosure: this change, the test, and the benchmarks were prepared with Claude Code (an AI coding assistant).
🤖 Generated with Claude Code

Summary
- Dev trailing-slash and base middleware return HTTP 400 on `decodeURI` failure instead of passing the error through (500)
- Static preview catches `fileURLToPath` failures from malformed paths and returns 400
Closes #18650
Test plan
- Repro gist from the issue: `/`, `/fixture/%`, `/fixture/%C0%AF` status codes

Changes
With all the workflow changes, it seems like something was broken, trying it out to see the logs (or maybe just have it working first try, that'd be cool)
Testing
We'll see
Docs
N/A

Changes
- Replaces the legacy compiler in the TypeScript plugin with
@astrojs/astro2tsx, which uses compiler-rs to generate virtual TSX and source mappings. - Declares the Node.js range
^20.19.0 || >=22.12.0and removes dependencies used only by the legacy converter.
Testing
- Adds coverage verifying that script and style contents stay out of virtual TSX.
- Existing plugin tests cover Astro references, completions, and implementations through the new converter.
Docs
Changeset
Made with AI.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| vscode-languageclient (source) | ^10.1.2 → ^11.0.0 |
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| vscode-jsonrpc (source) | ^9.0.3 → ^10.0.0 |
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/ts-plugin@1.11.0
Minor Changes
- #18647
f1c5a5fThanks @florian-lefebvre! - Updates the Node.js version requirement to^20.19.0 || >=22.12.0.
Patch Changes
- #18647
f1c5a5fThanks @florian-lefebvre! - Fixes TypeScript auto-import suggestions to use the.astrocomponent name instead of its generated TSX name.
astro@7.4.8
Patch Changes
- #18616
d747a53Thanks @florian-lefebvre! - Updates CLI argument parsing
@astrojs/react@7.1.5
Patch Changes
- #18664
1713dc0Thanks @ocavue! - Expands the peer dependency version range foroxc-transform-reactfrom^0.145.0to>=0.145.0 <0.157.0.
astro-vscode@2.17.3
Patch Changes
- #18649
39ede5fThanks @Princesseuh! - Publishes the Astro VS Code extension with the fix forsource.organizeImportsonly organizing imports in one region of.astrofiles that have both frontmatter and<script>tags

Changes
- In
validateForwardedHeaders(), a pattern without aprotocolfield in a mixedallowedDomainslist could previously pass anyX-Forwarded-Protovalue (e.g.ftp,ws) intoAstro.url. This happened becausematchProtocol()treatsundefinedas "any protocol", making a mixed list less strict than a uniform list or the documented allow-all[{}]. Protocol-less entries in a mixed list now fall back to the samehttp/https-only check used by the other configurations. - Patterns with an explicit
protocol(e.g.{ hostname: 'x', protocol: 'wss' }) are still matched exactly, so intentional non-http configurations are unaffected.
Testing
- Extended
packages/astro/test/units/app/node.test.tswith cases covering mixedallowedDomainslists: verifies thatftp,ws, and other non-http(s) values are ignored and do not reachAstro.url, whilehttpscontinues to pass through correctly.
Docs
- No docs update needed. The
security.allowedDomainsAPI is unchanged; this corrects an unintended permissiveness rather than a documented behavior.
Closes #18639
👋 long time no see - we just finished moving https://www.defined.net/docs and https://nebula.defined.net/docs to starlight from docusaurus - the move went great! Noticed that the default contrast was hard to see, was hoping I could maybe upstream a fix before @HiDeoo gets the Pagefind UI 2 PR in (which also fixes this b/c Pagefind fixed it in their v2 UI)
Description
- Pagefind's default UI styles the search input placeholder with
opacity: 0.2, and Starlight doesn't override it. With Starlight's default palette, the placeholder renders at 1.53:1 in light mode and 1.89:1 in dark, well below the 4.5:1 that WCAG 1.4.3 asks of text. Placeholder text isn't covered by any of the criterion's exceptions. - This PR sets the placeholder to
--sl-color-gray-3at full opacity: 7.02:1 light, 5.24:1 dark. It still reads as secondary next to the--sl-color-whiteinput text. - #4307 (Pagefind UI v2) also fixes this when it lands: Pagefind's component UI colors its placeholder with
--pf-text-muted, which that PR maps to--sl-color-gray-3. This picks the same token, so the placeholder looks the same before and after the migration. - We hit this on the Nebula docs and patched it locally in DefinedNet/nebula-docs#406.
Screenshots are from examples/basics, built before and after the change:
| Before | After | |
|---|---|---|
| Light | ![]() |
![]() |
| Dark | ![]() |
![]() |
🤖 Generated with Claude Code

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@7.4.7
Patch Changes
7da442bThanks @matthewp! - Fixes the image endpoint treating directories whose names differ only by letter case as being inside the build output directory on case-sensitive filesystems- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
- @astrojs/markdown-satteri@0.4.7
@astrojs/cloudflare@14.4.6
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
- @astrojs/underscore-redirects@1.0.4
@astrojs/markdoc@2.1.3
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
@astrojs/mdx@8.1.3
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
- @astrojs/markdown-satteri@0.4.7
@astrojs/netlify@8.2.12
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
- @astrojs/underscore-redirects@1.0.4
@astrojs/node@11.1.11
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
@astrojs/preact@6.1.2
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
@astrojs/react@7.1.4
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
@astrojs/vercel@11.0.20
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
@astrojs/internal-helpers@0.13.1
Patch Changes
7da442bThanks @matthewp! - Fixes the image endpoint treating directories whose names differ only by letter case as being inside the build output directory on case-sensitive filesystems
@astrojs/markdown-remark@7.3.6
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1
@astrojs/markdown-satteri@0.4.7
Patch Changes
- Updated dependencies [
7da442b]:- @astrojs/internal-helpers@0.13.1

Summary
- Register a single process
unhandledRejectionlistener with one sharedAsyncLocalStorage - Stops standalone from logging in-request rejections as "outside request context" and from setting
process.exitCode = 1
Closes #18624
Test plan

Part of the implementation of the enhanced content collections RFC (collection metadata).
Changes
- With
experimental.collectionMetadata,astro:build:donereceivescollections.metadata, the metadata of the build-time collections, andcollections.entries(name, { content }), their entries. This is for integrations that validate or post-process content after a build, without the workarounds they use today. - The metadata comes from
.astro/collections-metadata.json, written by sync. Entries come from the data store the build's sync wrote, which keeps every collection, so collections with a storage driver are included. Eachentries()call reads only its collection and keeps nothing: with a chunked data store only the collection's parts are read, and a single-file store is parsed whole and the other collections dropped on return. - Entries are plain data, with references and images unresolved.
content: falseleaves outbodyandrendered. Live collections and unknown names return no entries. Each integration gets its own copy of the metadata, and eachentries()call returns new objects. astro:build:donegets acollectionsoption, typed byBuildDoneCollections. The storage stack (#18632) addscollections.storageto the same option, so whichever lands second merges both fields.- Moves the metadata changesets here from #18596, so they stay in the last PR of the stack, and adds one for this hook.
Testing
collection-metadata.test.tsbuilds the fixture with an integration readingcollectionsinastro:build:done: the metadata of build-time collections, entries with and without content, and no entries for a live collection. Without the flag, the hook receives no metadata or entries.
Docs
- The changesets describe the feature. Docs will come with the experimental flag page.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- With
experimental.collectionStorageDrivers,astro:build:donereceivescollections.storage: a handle for each storage descriptor the build wrote a snapshot with. Each handle has thecollectionsit holds, thesnapshotthe build wrote,readAtRuntime(whether pages rendered on demand read it), and the driver'slistSnapshots()anddeleteSnapshot()when it implements them. - Astro never deletes snapshots: it can't know which ones deployed servers, deploy previews or rollback targets still read. Integrations that know decide, through the handles.
- The handle's
deleteSnapshot()throwsCollectionStorageSnapshotInUsewhen asked to delete the build's own snapshot whilereadAtRuntimeistrue. It can't protect the snapshots older deployments read. readAtRuntimeistruewhen the server renders a route on demand, except Astro's internal routes that never run project code (the image endpoint and the default 404 page). Server islands and actions count, as they run project code. Builds that skip the content sync, which only in-memory builds do, get no handles.syncInternal()returns the driver loader it used, so the build reuses the drivers sync created. They were loaded through Vite, which closes after sync.- Moves the storage changesets here from #18583, so they stay in the last PR of the stack, and adds the cleanup to them.
Testing
collection-storage-handles.test.tscovers the handles, the guard,readAtRuntime: false, and drivers withoutlistSnapshots()ordeleteSnapshot().collection-storage.test.tschecks the handles a real build passes to an integration.- The SQLite package's fixture, a static build, deletes its own snapshot in
astro:build:done, whichreadAtRuntime: falseallows.
Docs
- The changesets describe the feature. Docs will come with the experimental flag page.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/starlight-docsearch@0.8.1
Patch Changes
- #4337
c5d0a7fThanks @moonmeister! - Fixes DocSearch not loading when its script runs after the page has finished loading, for example when a Content Security Policy requires scripts to be added dynamically
@astrojs/starlight@0.42.10
Patch Changes
-
#4354
56b8587Thanks @jasikpark! - Improves the color contrast of the search input placeholder text -
#4337
c5d0a7fThanks @moonmeister! - Fixes search not loading when the search script runs after the page has finished loading, for example when a Content Security Policy requires scripts to be added dynamically -
#4352
3edab29Thanks @delucis! - Fixes the AstrotrailingSlashandbuild.formatoptions not being applied correctly to sidebar links that include a query string or hash

Changes
- Fixes a case where some dependency-resolution warning logic could throw and stop the build
- Made with AI
Testing
Adds regression tests
Docs
Changeset

Changes
- When
security.csp.scriptDirective.strictDynamicis enabled, Astro now emits a<script type="importmap">in<head>(before any module scripts) that maps every client.js/.mjsasset URL to its SHA digest. Browsers propagate the integrity metadata through dynamic imports, so<script src>entry points, the chunks they import, andimport()calls from<astro-island>all load without being blocked by'strict-dynamic'. - The hash of the import map itself, plus the hash of every hashed file, is added to
script-src. A newtrackScriptIntegrity()helper incore/csp/common.tsreads files from the client output on disk (avoiding thefor...in-over-Setbug in the oldtrackScriptHashes/trackStyleHashesloops that prevented any chunk hashes from reaching the policy). The deadfor...inloops are removed. Pages withoutstrictDynamicare unaffected.
Testing
- New unit tests in
packages/astro/test/units/csp/common.test.tscovertrackScriptIntegrity(): hash generation, import map structure, deterministic ordering, and query-string variants for adapters withassetQueryParams. - Integration tests added in
packages/astro/test/csp.test.tsverify that a built page withstrictDynamic: truecontains a<script type="importmap">with the expected integrity entries and that all file hashes appear inscript-src.
Docs
- The
strictDynamicJSDoc intypes/public/config.tsis extended to explain the import map behaviour and the minimum browser versions required (Chrome 127, Firefox 138, Safari 18). No separate docs-site update is needed beyond that inline note.
Closes #18607

Changes
spreadAttributesnow merges the scoped class into a copy of the spread object instead of into the object itself.- Before, spreading an object that outlives a render, like a constant imported from another module, appended the scoped class to that object on every render, so the rendered
classattribute kept growing per request (class="astro-abc astro-abc astro-abc") and the HTML of unchanged content differed between requests. {...Astro.props}was not affected, because the props are a new object on every render.- Adds a changeset.
Closes #18628
Testing
Adds two unit tests to test/units/render/html-primitives.test.ts: spreading an object with a scoped class leaves the object unchanged, and spreading the same object twice renders the same attributes. Both fail without the change and pass with it.
Also checked with the reproduction from the issue: with the change, the element gets the scoped class once on every request in astro dev, and the imported object stays unchanged.
Updates the existing Allows scoped classes with spread test in test/astro-basic.test.ts. Its fixture spreads the same object onto three elements, and only the first gets the scoped class passed in. Before this change, that class leaked into the shared object, so the other two rendered two class attributes (class="astro-xxx" class="has-class"), and the test passed on the leaked one. They now get only their own class; scoping still applies through data-astro-cid-*, which the test now checks for all three.
Docs
No docs change: this restores the behaviour you would expect from a spread, and the docs do not describe spreads as changing their source object.

Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| node (source) | major | 24.22.2 → 26.13.0 |
|
| node | uses-with | major | 24.22.2 → 26.13.0 |
| node (source) | final | major | 24.20.0-bullseye → 26.8.1-bullseye |
Release Notes
nodejs/node (node)
v26.13.0: 2026-10-28, Version 26.13.0 'Lithium' (LTS), @richardlau
Notable Changes
This release marks the transition of Node.js 26.x into Long Term Support (LTS)
with the codename 'Lithium'. It will continue to receive updates through to
the end of April 2029.
Other than updating metadata, such as the process.release object, to reflect
that the release is LTS, no further changes from Node.js 26.12.1 are included.
If you are updating from an earlier Long Term Support release (e.g. Node.js 24
or 22 or earlier) please note that since Node.js 25 the official binaries for
Linux are linked against libatomic, which may need to be installed separately
depending on your Linux distribution.
v26.12.1: 2026-10-21, Version 26.12.1 (Current), @aduh95 prepared by @RafaelGSS
This is a security release.
Notable Changes
- (CVE-2026-106069, CVE-2026-106072) tls: reject non-canonical IP addresses (Matteo Collina) – High
- (CVE-2026-105482) dns: validate resolve inputs for null bytes (James M Snell) – High
- (CVE-2026-105483) tls: fix ip normalization regression (James M Snell) – High
- (CVE-2026-111497) src: expose
BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH(Antoine du Hamel) – High - (CVE-2026-111497) deps: brotli: cherry-pick
0ed4268(Evgenii Kliuchnikov) – High - (CVE-2026-105481) http: ensure agent data guard works without I/O (James M Snell) – Medium
- (CVE-2026-106074) crypto: reset random caches across snapshots (Filip Skokan) – Medium
- (CVE-2026-106070) zlib: avoid caching invalid ZIP local headers (Matteo Collina) – Low
- (CVE-2026-106071) src: fix the fs permission tree node on wildcard nodes (James M Snell) – Low
- (CVE-2026-106073) permission: check permission model in realpathSync (RafaelGSS) – Low
- deps: V8: backport
93cd21e(Joyee Cheung) - crypto: update root certificates to NSS 3.131.1 (Antoine du Hamel)
- tls: reject chains containing blocked public keys (Ulises Gascon)
- deps: update c-ares to 1.34.9 (Node.js GitHub Bot)
- tools: retry Gatekeeper check and stapling after notarization (Ryan Aslett)
- crypto: harden X.509 conversion and formatting (Filip Skokan)
Commits
- [
818e4ca061] - crypto: update root certificates to NSS 3.131.1 (Antoine du Hamel) #66877 - [
fd3c87ed43] - crypto: harden X.509 conversion and formatting (Filip Skokan) nodejs-private/node-private#966 - [
acffa610db] - crypto: reset random caches across snapshots (Filip Skokan) nodejs-private/node-private#987 - [
7895a5cd2d] - deps: update undici to 8.12.2 (Node.js GitHub Bot) #66721 - [
12daa54d2e] - deps: V8: backport93cd21e(Joyee Cheung) nodejs-private/node-private#999 - [
6a8b3db7e2] - deps: update c-ares to 1.34.9 (Node.js GitHub Bot) #66868 - [
a6040b50d9] - deps: brotli: cherry-pick0ed4268(Evgenii Kliuchnikov) nodejs-private/node-private#1002 - [
6b78ea171d] - dns: validate resolve inputs for null bytes (James M Snell) nodejs-private/node-private#984 - [
0683ee5f7d] - http: ensure agent data guard works without I/O (James M Snell) nodejs-private/node-private#983 - [
e5cae10148] - Revert "module: synchronously load most ES modules" (Antoine du Hamel) #66786 - [
cc244131aa] - permission: check permission model in realpathSync (RafaelGSS) nodejs-private/node-private#973 - [
0392385841] - src: exposeBROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH(Antoine du Hamel) nodejs-private/node-private#1002 - [
c273a408c9] - src: fix the fs permission tree node on wildcard nodes (James M Snell) nodejs-private/node-private#986 - [
a2caddd20e] - tls: reject chains containing blocked public keys (Ulises Gascon) #66871 - [
ad788ccd07] - tls: reject non-canonical IP addresses (Matteo Collina) nodejs-private/node-private#982 - [
cd4b05469c] - tls: fix ip normalization regression (James M Snell) nodejs-private/node-private#985 - [
5fa440e0d7] - tools: retry Gatekeeper check and stapling after notarization (Ryan Aslett) #66855 - [
745ad77156] - zlib: avoid caching invalid ZIP local headers (Matteo Collina) nodejs-private/node-private#981
v26.12.0: 2026-10-14, Version 26.12.0 (Current), @richardlau
Notable Changes
- [
1ebd6d3677] - (SEMVER-MINOR) doc,lib,src: throw on missing WebAssembly or RX support (Paolo Insogna) #66533 - [
7f1937d2b9] - (SEMVER-MINOR) http: add websocketMask() and websocketUnmask() (James M Snell) #66335
Commits
- [
30e76bb16a] - benchmark: fix input passed to subtle.digest in webcrypto-digest (Rafael Gonzaga) #66608 - [
adef72223a] - benchmark: fix buffer option in buffer read/write benchmarks (Rafael Gonzaga) #66604 - [
2f498f08fe] - benchmark: add util.parseArgs benchmark (Rafael Gonzaga) #66599 - [
4ce8412e18] - benchmark: fix url-searchparams-sort to sort a fresh list (RafaelGSS) #66535 - [
493bd6c66e] - benchmark,tools: fix napi benchmarks on GHA (Nigro Simone) #66423 - [
e4515552d6] - build: run QUIC CI for V8 changes (Yuya Inoue) #66602 - [
a888e51062] - build: support Python 3.15 (Mike McCready) #65750 - [
2afab9a63b] - build: do not include shared gtest innodelink path (Antoine du Hamel) #66626 - [
f88c2f8ec6] - build,test: enable temporal support on no-ICU and system-ICU builds (Antoine du Hamel) #66697 - [
5fd03e6fdf] - child_process: propagate config-file permission flags to children (Rafael Gonzaga) #66559 - [
f771134b07] - crypto: isolate provider EC PKCS8 encoding (Filip Skokan) #66413 - [
4e00a293db] - crypto: remove key export and metadata locks (Filip Skokan) #66413 - [
bcd8018775] - crypto: remove verify setup key locking (Filip Skokan) #66413 - [
883250fee2] - crypto: remove KEM key locking (Filip Skokan) #66413 - [
9d98805071] - crypto: remove RSA-OAEP key locking (Filip Skokan) #66413 - [
d6293e7bb1] - crypto: skip secret key mutex allocation (Filip Skokan) #66413 - [
8d8af8003e] - crypto: keep the root cert store per Environment (Shelley Vohr) #66411 - [
c6f0614785] - crypto: remove select Web Crypto warnings (Filip Skokan) #66312 - [
e5360b5a08] - deps: update googletest to988ea2c(Node.js GitHub Bot) #66652 - [
7eb230a2c1] - deps: update acorn to 8.19.0 (Node.js GitHub Bot) #66655 - [
af946ba8f3] - deps: update sqlite to 3.54.0 (Node.js GitHub Bot) #66663 - [
007872a85d] - deps: V8: cherry-pick8d14d49(Antoine du Hamel) #66627 - [
f44aec4966] - deps: update simdjson to 5.0.3 (Daniel Lemire) #66620 - [
1a33e914e8] - deps: V8: cherry-pick7d5eb1d(inoway46) #66566 - [
3294d51e5a] - diagnostics_channel: fix default callback context (Matteo Collina) #66481 - [
5c602a5824] - doc: list futimes among fd APIs disabled by the permission model (Rafael Gonzaga) #66649 - [
eaeb4736c8] - doc: add Test Runner to list of built-in diagnostic channels (Vas Sudanagunta) #66563 - [
0e1c99afae] - doc: document stream/iter behaviors and Node.js extensions (James M Snell) #66483 - [
846236367d] - doc: document URL and Uint8Array references in process.permission (Rafael Gonzaga) #66557 - [
fc3b067be7] - doc: clarify http Agent keepSocketAlive behavior (Efe Karasakal) #66252 - [
73a4e90ce2] - doc: document keepAliveTimeoutBuffer server option (Efe Karasakal) #66286 - [
bb816582af] - doc: fix request.reusedSocket timeout example (Efe Karasakal) #66286 - [
82223ab4d9] - doc: clarify revert PR label policy (Antoine du Hamel) #66529 - [
c6f59d4e8e] - doc: clarify node binary misuse after compromise (Rafael Gonzaga) #66530 - [
8904178498] - doc: document linux-x64-musl build toolchain (Issac) #66523 - [
1e8247a74e] - doc: run license-builder (github-actions[bot]) #66517 - [
b2773d5e4c] - doc: add missing return types in cluster.md (Daniel Pinto) #66453 - [
1ebd6d3677] - (SEMVER-MINOR) doc,lib,src: throw on missing WebAssembly or RX support (Paolo Insogna) #66533 - [
c1073f31de] - ffi: fix exportArrayBuffer type check (Trivikram Kamat) #66455 - [
69148ee0ff] - fs: lock FileHandle on first read in pull() and pullSync() (James M Snell) #66483 - [
700c60a1cd] - fs: serialize FileHandle writer() async writes (James M Snell) #66483 - [
32833def1c] - http: reduce raw header name allocations (Roberto Bianchi) #66488 - [
7f1937d2b9] - (SEMVER-MINOR) http: add websocketMask() and websocketUnmask() (James M Snell) #66335 - [
115731dda7] - http2: speed up response getHeaders (Roberto Bianchi) #66592 - [
447c36cb45] - lib: fix AbortSignal.any() nested composite leak (Darius) #66617 - [
1722ced4b4] - lib: add --allow-fs-vfs to permission available flags (Rafael Gonzaga) #66554 - [
062ece77fc] - lib: fix benchmark record acknowledgement race (Filip Skokan) #66430 - [
05d0b14438] - lib: set exit code on failed node:bench run() (RafaelGSS) #66534 - [
2cab299471] - lib: default node:bench warmup to 10 invocations (RafaelGSS) #66536 - [
83f507845d] - meta: bump nodejs/node-pr-labeler todfe5eb3(Soul Lee) #66606 - [
6fbffd5ee5] - meta: bump codecov/codecov-action from 7.1.0 to 7.1.1 (dependabot[bot]) #66448 - [
bd567f8bd6] - module: fix require of imports with package map (Lazizbek Ergashev) #66565 - [
c442f471a5] - module: synchronously load most ES modules (Geoffrey Booth) #62530 - [
51f66f0134] - permission: keep explicit fs grants when dropping a covering directory (Rafael Gonzaga) #66556 - [
1aa10d80e2] - process: mark process.finalization as release candidate (Matteo Collina) #66436 - [
dd4715a6ba] - querystring: fix value decoding after encoded keys (Ved Chaudhari) #66553 - [
9648a6ba8e] - quic: reject closed stream writer writes with a TypeError (James M Snell) #66483 - [
d6f566baf8] - quic: give each BindingData its own allocator state (Shelley Vohr) #66411 - [
c3204c15bd] - quic: validate session close error codes (Christian Aurich Zanettini Martins) #66302 - [
5b87354f5a] - quic: destroy stream on invalid promise body (Christian Aurich Zanettini Martins) #66260 - [
9ef698c781] - sqlite: validate aggregate() name and options (Guilherme Araújo) #66463 - [
bbf41f8cfb] - sqlite: persist enableDefensive() across reopen (Trivikram Kamat) #66404 - [
54867cd25e] - sqlite: throw on oversized strings instead of aborting (Trivikram Kamat) #66521 - [
4314cde48b] - src: release uv_fs_t in permission WildcardIfDir (Rafael Gonzaga) #66555 - [
0e58916f08] - src: stop including simdjson.h from env.h (Daniel Lemire) #66620 - [
06f56a55bb] - src: use native CopyArrayBufferBytes for webstream buffer copy (René) #66400 - [
2e3dd5bb63] - src: fix config file handling (Marco Ippolito) #66431 - [
cd86506bc2] - src: mark config file as stable (Marco Ippolito) #66431 - [
15ff9884e4] - stream: skip idle webstreams start and watchers (Matteo Collina) #66424 - [
3f75c89fb8] - stream: add pipeToSync() failOnIncompleteClose option (James M Snell) #66483 - [
6cecf140e7] - stream: do not fail the writer when pipeToSync() cannot close (James M Snell) #66483 - [
16833534b6] - stream: fix fromSync() async input error messages (James M Snell) #66483 - [
af41622ad8] - stream: reject closed fromWritable() writes with a TypeError (James M Snell) #66483 - [
4b83c6c38e] - stream: accept explicit stream/iter budgets below 16384 (James M Snell) #66483 - [
f302fbd04a] - stream: reduce per-chunk overhead in stream/iter consumers (James M Snell) #66483 - [
7ba60dcdbe] - stream: keep the original error when writer.fail() throws (James M Snell) #66483 - [
dcac51a7db] - stream: align pull() abort handling with the spec (James M Snell) #66483 - [
995dee6b6b] - stream: honor stream/iter protocols on function objects (James M Snell) #66483 - [
6eaf91353a] - stream: do not hold back nested async data in from() (James M Snell) #66483 - [
69d44aedb4] - stream: bound pre-batched async values in from() (James M Snell) #66483 - [
6b1e7c4cf1] - stream: guard shareSync() against re-entrant source reads (James M Snell) #66483 - [
8a47365425] - stream: split oversized share batches under drop-oldest (James M Snell) #66483 - [
30cbc4e643] - stream: reject drop-newest backpressure in shareSync() (James M Snell) #66483 - [
42ae08594e] - stream: detach shareSync consumers on strict budget errors (James M Snell) #66483 - [
fa49de9ba6] - stream: keep share buffer when all consumers detach (James M Snell) #66483 - [
e6662cb904] - stream: fix Utf8Stream flush handling (James M Snell) #66473 - [
93596b1a9e] - stream: add dump()/dumpSync() for stream/iter (Ethan Arrowood) #65598 - [
4ba6ce1b0c] - stream: port remaining SonicBoom tests for Utf8Stream (Matteo Collina) #66275 - [
cd8b5fa5b0] - test: tolerate async block count updates in test-fs-stat-bigint (Rafael Gonzaga) #66576 - [
30814ce991] - test: replace discard loops with dump() (Ethan Arrowood) #65598 - [
20441b8fc0] - test: run node-bench tools test sequentially (Filip Skokan) #66338 - [
9618da6fe3] - test: remove duplicated cases in permission fs-read fixture (Rafael Gonzaga) #66450 - [
c348a4cb46] - test: run instantiateStreaming-bad-imports WPT (Filip Skokan) #66322 - [
7d4fda6ba7] - test: honor allowed WPT promise rejections (Filip Skokan) #66322 - [
d4c87eb086] - test: scope Blob WPT failures to big-endian (Filip Skokan) #66322 - [
7309ddf204] - test_runner: rerun failing todo tests in suites (Barak) #66605 - [
da908b3072] - test_runner: report load errors with --test-isolation=none (Lazizbek Ergashev) #66550 - [
b18e121625] - test_runner: add mock call assertions to t.assert (Guilherme Araújo) #66476 - [
3d691ab75e] - tools: restore Python 3.14 for daily WPT (Filip Skokan) #66699 - [
714aca1ef6] - tools: switch to PGP and SHA256 in ICU updater (Antoine du Hamel) #66469 - [
fa9fca45e4] - tools: lint thread_local in src (Shelley Vohr) #66411 - [
dbc3e97847] - tools: copy hdr_histogram_internal.h in update-histogram.sh (Filipe Oliveira (Redis)) #66528 - [
4760c27904] - tools: bump the eslint group in /tools/eslint with 5 updates (dependabot[bot]) #66445 - [
63c20ee58e] - vfs: add ComposableProvider for layered mounts (Matteo Collina) #66235 - [
ab057989af] - watch: strip underscore aliases of watch flags (Trivikram Kamat) #66365
v26.11.1: 2026-10-07, Version 26.11.1 (Current), @aduh95
Commits
- [
2dc4638e85] - Revert "build: toggle doc-kit verbosity based on V" (Antoine du Hamel) - [
3febbc54ec] - Revert "build, doc: move to redesign" (Antoine du Hamel) - [
173250e2e7] - Revert "tools: bump the doc group in /tools/doc with 4 updates" (Antoine du Hamel)
v26.11.0: 2026-10-07, Version 26.11.0 (Current), @aduh95
Notable Changes
- [
232f178825] - (SEMVER-MINOR) buffer: addisLatin1(James M Snell) #66298 - [
27778036de] - (SEMVER-MINOR) buffer: addBuffer.stringLength()(Matteo Collina) #66064 - [
4f84c4bda2] - build, doc: move to redesign (Aviv Keller) #62045 - [
6f6296fef9] - (SEMVER-MINOR) doc: promote Alpine Linux to tier 2 support (Stewart X Addison) #63737 - [
e998d260d0] - (SEMVER-MINOR) http: addisValidHeaderName()and isValidHeaderValue() (James M Snell) #66334 - [
7702a50e08] - (SEMVER-MINOR) http2: addconnectionWindowSizeoption (Tim Perry) #65619 - [
e06aa62cec] - (SEMVER-MINOR) perf_hooks: fix truncation ofmonitorEventLoopDelay()resolution (James M Snell) #66115 - [
ee126e37e8] - (SEMVER-MINOR) perf_hooks: allowRecordableHistogramto record 0 (James M Snell) #66114 - [
1fef8f54db] - (SEMVER-MINOR) perf_hooks: addhistogram.diff()(James M Snell) #66099 - [
f1b9758c4e] - (SEMVER-MINOR) perf_hooks: addhistogram.snapshot()(James M Snell) #66099 - [
291d56ea3e] - (SEMVER-MINOR) perf_hooks: harden histogram CBOR import validation (James M Snell) #66098 - [
6299b09d5c] - (SEMVER-MINOR) process: graduateprocess.ref/unrefto stable (James M Snell) #66213 - [
41d6707b63] - (SEMVER-MINOR) sqlite: renameDatabaseSyncandStatementSync(Guilherme Araújo) #65988 - [
60d0aa0cd4] - (SEMVER-MINOR) src: add--process-timeout=N(James M Snell) #66138 - [
f39916a7e3] - (SEMVER-MINOR) src: expose size and count in heap profile output (Ilyas Shabi) #65737 - [
0b00d5ea59] - (SEMVER-MINOR) src: let embedders exempt linked bindings from the addon permission (Shelley Vohr) #66067
Commits
- [
11c3d7115d] - benchmark: add implicit-framing case to http/set-header (Matteo Collina) #66420 - [
168b764fec] - benchmark: add zstdCompress benchmark (James Ross) #66358 - [
69182564a7] - benchmark: add a node::MakeCallback benchmark (Nigro Simone) #66316 - [
12e540582f] - (SEMVER-MINOR) benchmark: add http header validator benchmark (James M Snell) #66334 - [
e6abdf6b01] - benchmark: remove duplicate ffi string length direct (Donghoon Kang) #66278 - [
480ca7cc55] - benchmark: fix shadowing that broke h=20 on incoming_headers benchmark (Tim Perry) #66257 - [
c6bbc1b128] - benchmark: cover Web Crypto conversion costs (Filip Skokan) #66237 - [
85a2e4e270] - benchmark: remove duplicate ffi add-64 benchmark (Soul Lee) #66121 - [
d0a72f2c12] - buffer: fix negative index for large buffers (Hilary Asogwa) #66325 - [
b7f6a66a9f] - (SEMVER-MINOR) buffer: add isLatin1 (James M Snell) #66298 - [
232f178825] - (SEMVER-MINOR) buffer: add isLatin1 (James M Snell) #66298 - [
f7d3d11c11] - buffer: fix odd UTF-16LE indexOf start (Yuya Inoue) #65960 - [
27778036de] - (SEMVER-MINOR) buffer: add Buffer.stringLength() (Matteo Collina) #66064 - [
9f1db461d2] - build: update common.gypi for z/OS (Gaby Baghdadi) #66449 - [
0002037b3f] - build: update configure.py for z/OS (Gaby Baghdadi) #66449 - [
a341ac460a] - build: fix vcbuild format-md install and exit (Ved Chaudhari) #66475 - [
bec52d9103] - build: fix vcbuild lint skipping lint-md-build (Ved Chaudhari) #66467 - [
9acdb5910c] - build: toggle doc-kit verbosity based on V (Brian Muenzenmeyer) #66293 - [
6ee32f857a] - build: support LIEF 0.17.x and 1.x (Yuya Inoue) #66240 - [
2248869955] - build: add clang support for pgo on macOS/Linux (Chengzhong Wu) #66136 - [
49069529eb] - build: add GZIP_COMPRESSION Make variable (inoway46) #66228 - [
9066d33aa2] - build: portmake_temporal_zoneinfo_cppto GYP (Antoine du Hamel) #66183 - [
1f4a8fb1cb] - build: addv8_enable_temporal_systemicu(Steven R. Loomis) #65992 - [
4f84c4bda2] - build, doc: move to redesign (Aviv Keller) #62045 - [
a0e7141ffc] - child_process: build the default env block in one native pass (Shelley Vohr) #65325 - [
9fa31096d4] - crypto: improve random synchronous number generation performance (Mert Can Altin) #66348 - [
53cde9d1f8] - crypto: fix raw key export error for wrong key type (한국) #66217 - [
32ba6d5ada] - crypto: use backend cSHAKE and KMAC (Filip Skokan) #66237 - [
67ccff6434] - crypto: separate conversion from validation (Filip Skokan) #66237 - [
ceeb37173d] - crypto: verify empty KMAC outputs (Filip Skokan) #66237 - [
359b07a641] - crypto: check EC coordinate conversion results (Filip Skokan) #66237 - [
e4d746c4a5] - crypto: map JWK export failures to OperationError (Filip Skokan) #66237 - [
a851dda86a] - crypto: include EC public keys in PKCS8 exports (Filip Skokan) #66237 - [
7f58476ed1] - crypto: use the public CryptoKey prototype (Filip Skokan) #66237 - [
75870623ad] - crypto: split hybrid keys without species (Filip Skokan) #66237 - [
a1bea87c6a] - crypto: report actual RSA modulus lengths (Filip Skokan) #66237 - [
5e04680036] - crypto: derive Argon2 without worker threads (Filip Skokan) #66237 - [
fe09120a0e] - crypto: create key usage arrays without species (Filip Skokan) #66237 - [
44a2965f5f] - crypto: minimize RSA public exponent metadata (Filip Skokan) #66237 - [
2f3e6dff9d] - crypto: copy derived bits without species (Filip Skokan) #66237 - [
d54a2b2049] - crypto: handle PBKDF2 iteration limits (Filip Skokan) #66237 - [
2ef6046f11] - crypto: reject duplicate unknown key usages (Filip Skokan) #66237 - [
2e25ae4a7a] - crypto: check RSA JWK alg with SHA-3 hashes (Filip Skokan) #66237 - [
0370e02e2a] - crypto: copy parameters without array species (Filip Skokan) #66237 - [
e042d35ca5] - crypto: convert importKey data as a union (Filip Skokan) #66237 - [
ff86606768] - crypto: copy detached parameters as empty (Filip Skokan) #66237 - [
1314d277b2] - crypto: resolve supports overloads by type (Filip Skokan) #66237 - [
a855a46aeb] - crypto: allow unbound SubtleCrypto.supports (Filip Skokan) #66237 - [
4a72c1d690] - crypto: allow short AES-GCM IVs (Filip Skokan) #66237 - [
2d84b7ed49] - crypto: validate normalized hash names (Filip Skokan) #66237 - [
6bfd3924ff] - crypto: convert getRandomValues views (Filip Skokan) #66237 - [
529bd18c1a] - crypto: isolate cipher job errors (Filip Skokan) #66237 - [
d4af11e171] - crypto: reject short AES-KW inputs (Filip Skokan) #66237 - [
78374c8af0] - crypto: match algorithm names as ASCII (Filip Skokan) #66237 - [
ab9a3f2b01] - crypto: use internal random buffer bounds (Filip Skokan) #66237 - [
7c9b2df87a] - crypto: use current FIPS state for availability (Filip Skokan) #66160 - [
55af1dcded] - crypto: update root certificates to NSS 3.129 (Node.js GitHub Bot) #66496 - [
4387cb46d2] - deps: update timezone to 2026e (Node.js GitHub Bot) #66419 - [
150c96ef3f] - deps: V8: cherry-pickc795f59(Aviv Keller) #66380 - [
6b5ac2ab5d] - deps: update archs files for openssl-3.5.9 (Node.js GitHub Bot) [#66396](https://redirect.github.com/nodejs/node/p
[!IMPORTANT]
✂ PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| sitemap | ^9.0.1 → ^10.0.0 |
Release Notes
ekalinin/sitemap.js (sitemap)
v10.0.0
[BREAKING CHANGES]
Dropped CommonJS build — the package is now ESM-only
require('sitemap')is no longer supported on Node versions without
built-inrequire(esm). Thedist/cjsbuild, therequireexport condition,
andtsconfig.cjs.jsonare all gone;exportsnow resolves todist/index.js
for every consumer. Migrate toimport { SitemapStream } from 'sitemap'.- Node.js >=22.22.1 now required (previously >=20.19.5). CommonJS
consumers can still load this package throughrequire(esm), which landed
unflagged in 22.12; the floor is 22.22.1 to match the development toolchain. - Build output flattened from
dist/esm/*anddist/cjs/*todist/*. The
binentry is nowdist/cli.js.
simpleSitemapAndIndex defaults to 45,000 URLs per sitemap
- The default
limitdrops from 50,000 to 45,000, the same default
SitemapAndIndexStreamand the CLI already use (DEFAULT_SITEMAP_ITEM_LIMIT).
The headroom keeps rich entries (images, video, news) under the 50MB
uncompressed file-size limit. A 50,000-URL input now produces two sitemap
files instead of one; passlimit: 50000to keep the old output.
SitemapStream writes an empty sitemap instead of erroring
- Ending a
SitemapStreamwithout writing any items now produces a
well-formed empty<urlset>instead of failing withEmptySitemap
(#394, #421). This matchesSitemapIndexStream, which already wrote an empty
<sitemapindex>.EmptySitemapis still exported but deprecated and no
longer thrown. An empty<urlset>does not pass strictsitemap.xsd
validation, which requires at least one<url>; search engines accept it.
One logger option across the library; xmlNS renamed to xmlns
SitemapStream,SitemapIndexStream,SitemapAndIndexStreamand
simpleSitemapAndIndexaccept the sameloggeroption the parsers already
had (#348). Validation warnings that went straight toconsole.warnnow go
through it. Passfalseto silence. TheLoggertype is now exported.- Invalid news and video attribute values now go through
errorHandler(and
so the logger) like every other validation error, instead of a hardcoded
console.warn. The warning text is now the error's name and message, which starts with
the item's URL. UnderErrorLevel.THROWa customerrorHandlerreceives
these errors too, like every other validation error; the default handler
still throws. - The
SitemapStreampropertyxmlNSis nowxmlns, matching the option
name (#300).xmlNSstill works as a deprecated alias.SitemapStream.errorHandleris always set now; it defaults to
a handler that warns throughlogger.
Both XML parsers share one error store and entry cap
XMLToSitemapItemStream and XMLToSitemapIndexStream now extend one internal
base class, so they report errors and cap entries the same way.
XMLToSitemapIndexStream.erroris a read-only getter for the first error
(errors[0], ornull). Assigning to it now throws aTypeErrorin strict
mode. The index parser also gains theerrorsarray (capped at
LIMITS.MAX_PARSER_ERRORS) anderrorCount, where it previously kept only
the first error.XMLToSitemapItemStreamreports a sitemap with more than 50,000<url>
entries once, instead of logging and recording an error for every dropped
entry, soerrorCountand the log no longer grow with the overflow. It
gains the index parser'smaxEntriesoption,entryCountproperty and
'maxEntriesExceeded'event, and anerrorgetter.urlCountstill works
as a deprecated alias forentryCount.parseSitemapstill resolves with
the first 50,000 items, but it now stops reading once the cap is crossed
and destroys the source stream, asparseSitemapIndexalready did.- Both parsers now fail on a truncated document (an element left unclosed
when the input ends), like any other malformed XML. Before, the
unfinished entry was dropped silently.parseSitemapand
parseSitemapIndexreject in that case, andparseSitemapnow also
rejects when the source stream fails instead of never settling. - The index parser's warnings for an invalid
<loc>or<lastmod>are now
logged as one message, the same text recorded inerrors. The recorded
lastmod error now readsInvalid lastmod date format in sitemap index: ….
SitemapAndIndexStream destroys itself on error
- When a sitemap stream errors, or
getSitemapStreamthrows or returns an
invalid tuple,SitemapAndIndexStreamnow destroys itself and emits the
error once. It used to emit the error without stopping, so the same failure
could be emitted twice, and agetSitemapStreamfailure was followed by a
genericNo sitemap stream availableerror. Code that listened forerror
and kept writing now gets write-after-destroy errors instead.
sitemap --index --gzip names sitemaps sitemap-N.xml.gz
- With
--gzip,sitemap --indexnow writes each sitemap tositemap-N.xml.gz
and lists that URL in the index, assimpleSitemapAndIndexalready did. It
used to write gzipped data tositemap-N.xmland index it under that name,
so crawlers fetched gzip bytes from a.xmlURL. Update scripts that upload
or servesitemap-*.xmlafter a gzipped run.
SitemapStream reports item errors as stream errors
SitemapStreamandSitemapItemStreamnow report a failure on an item
through the stream:write()no longer throws, and the stream emits
errorand is destroyed. This covers an invalid item at
ErrorLevel.THROW, an itemnormalizeURLrejects (such as an invalid
lastmod), and an item that can't be serialized (such as a non-string
video attribute atErrorLevel.SILENT). Before, the error was thrown out
ofwrite(), so a piped source crashed the process with an uncaught
exception. Code that wrappedwrite()intry/catchmust listen for
errorinstead, or usepipeline().SitemapStreamchecksxmlns.customin its constructor, so an invalid
custom namespace now throws fromnew SitemapStream()instead of from the
firstwrite().SitemapStreamserializes each item itself instead of piping it through an
internalSitemapItemStream, so it now outputs one chunk per item. The XML
is unchanged.
Stricter priority and alternate-link validation
- A
priorityofNaNis now reported as aPriorityInvalidError: it
throws atErrorLevel.THROWand warns atWARN. It used to skip
validation and write<priority>NaN</priority>at every level. - An alternate link with no
langorhreflangis now reported as the new
InvalidLinkHreflangerror atWARNandTHROW, and dropped from the
output atWARNandSILENT.SitemapItemStream, which doesn't
validate, drops it too, with no warning. Every level used to fail with a
TypeErrorfrom the XML writer. Writing the link withouthreflangwould
produce theandroidLinkmarkup, which parses back asandroidLink.
Error classes are exported by name; UndefinedTargetFolder removed
index.tslists the error classes explicitly instead of
export * from './lib/errors.js', like the public types, so a new error
class is public only once it is added there.UndefinedTargetFolderis removed. Nothing has thrown it since 7.0.0,
which removedcreateSitemapsAndIndex, its only user.
Changed
- The CLI parses arguments with Node's built-in
util.parseArgsinstead of
theargpackage, which is no longer a dependency (#471). Unknown options
and a non-integer--limitnow print a message and exit with code 2 instead
of throwing an uncaught error. - Test suite migrated from Jest to the built-in Node.js test runner. Coverage
thresholds moved fromjest.config.cjsinto thetest:coveragescript and are
enforced in CI by a dedicated job. - CI now runs on Linux, Windows and macOS across Node 22/24/26. Lint, formatting
and typechecking run once rather than on every matrix leg. - Stricter
<loc>validation in the sitemap parser:XMLToSitemapItemStream
now validates<loc>values with the samevalidateURLused by the sitemap
index parser, adding a URL-parseability check on top of the existing length
and protocol checks. A malformed URL that passed the old checks but fails
new URL()is now dropped with a warning (or throws under
ErrorLevel.THROW). Warn/error messages for invalid<loc>values changed to
theInvalid URL in sitemap: …form. validateURLthrowsInvalidURLError, a new subclass of
InvalidHostnameError(soinstanceof InvalidHostnameErrorstill matches).
Its message readsInvalid URL "…": …instead ofInvalid hostname "…": …,
and it shows at most the first 100 characters of the offending value.- Stricter video validation in
validateSMIOptions: a videoduration,
ratingorview_countthat isNaN,Infinityor otherwise non-numeric
is now reported as invalid (and throws underErrorLevel.THROW). Previously
only out-of-range finite numbers were caught, soNaNslipped through. XMLToSitemapItemStreamnow buffers each element's character data and
handles it once at the next tag boundary: text and CDATA chunks within one
element are joined, surrounding whitespace is trimmed for CDATA as it already
was for text, whitespace between chunks is kept (Episode <![CDATA[One]]>
now parses asEpisode One, notEpisodeOne), and stray character data
between elements is reported against
the enclosing element instead of overwriting the previous one. Character data
longer thanLIMITS.MAX_PARSER_CHAR_DATA_LENGTH(64 KiB) for one element is
dropped with a warning.- Internal: the parser's duplicated
text/cdataSAX handlers were collapsed
into one, and its inline bounds checks (priority, video duration/rating/view
count, ISO dates) now delegate to shared guards inlib/validation.ts, with
the bounds defined once inLIMITS. XMLToSitemapIndexStreamnow handles character data the same way: text and
CDATA within one<loc>or<lastmod>are joined and trimmed, stray
character data is reported against the enclosing element, and values longer
thanLIMITS.MAX_PARSER_CHAR_DATA_LENGTHare dropped with a warning.
Unhandled CDATA is now logged asunhandled text for tag:instead of
unhandled cdata for tag:. Both parsers share one buffer,
createCharDataBufferinlib/utils.ts.XMLToSitemapIndexStreamenforces the 50,000-entry spec limit itself.
Entries pastLIMITS.MAX_SITEMAP_ITEM_LIMITare dropped with a single error
(which throws underErrorLevel.THROW), and a newentryCountproperty counts
every<sitemap>seen. Previously only theparseSitemapIndexwrapper capped
entries, so piping the stream directly had no limit.parseSitemapIndexstill
rejects an over-limit index and stops reading as soon as the limit is crossed,
but amaxEntriesabove 50,000 no longer raises the limit. A new
maxEntriesstream option lowers the cap, or raises it (Infinityturns it
off) for callers that knowingly parse oversized indexes. When the cap is
crossed the stream emits'maxEntriesExceeded', and logs the overflow only
if nothing listens for that event, soparseSitemapIndexrejects without
also logging.maxEntries: 0is allowed (nothing is emitted, and
parseSitemapIndexrejects on the first entry); a negative, fractional or
NaNvalue is rejected, andparseSitemapIndexdestroys the source stream
before rejecting.- Errors that
simpleSitemapAndIndexandSitemapAndIndexStreamwrap, such
asFailed to write sitemap files: …or agetSitemapStreamfailure, now
carry the original error ascause. SaxParserStreamOptions, the shared base ofXMLToSitemapItemStreamOptions
andXMLToSitemapIndexItemStreamOptions, is exported.LIMITSgains the bounds the validators use:MIN_PRIORITY,
MAX_PRIORITY,PRIORITY_STRING_REGEX,MIN_VIDEO_DURATION,
MAX_VIDEO_DURATION,MIN_VIDEO_RATING,MAX_VIDEO_RATINGand
MIN_VIDEO_VIEW_COUNT.LIMITS.MAX_URL_ENTRIESis deprecated. Nothing reads it; the parsers cap
entries atLIMITS.MAX_SITEMAP_ITEM_LIMIT(the same value), which their
maxEntriesoption overrides.
Fixed
- A string
priorityno longer crashesSitemapStreamwith
item.priority.toFixed is not a function(#393). A plain decimal string
such as'0.5'or'.5'is converted to a number (hex, binary and
exponent forms such as'0x1'or'1e-1'are not), and
SitemapItemLoose.prioritynow acceptsnumber | string. Any other value,
including an empty string, is reported as aPriorityInvalidErrorat
WARNandTHROW, and written as given atWARNandSILENT, like other
invalid values.isValidPriorityrejects non-numbers instead of coercing
them. isValidYesNoaccepts only a wholeyes,Yes,YES,no,NoorNO.
Its unanchored alternation used to accept any value that started withYES,
containedNOoryes, or ended inno, such asNOPEormaybe-yes, so
the parsers andvalidateSMIOptionslet those values through.XMLToSitemapItemStreamreports an invalidvideo:requires_subscription,
video:family_friendly,video:liveorplayer_locallow_embedvalue as a
warning and a parse error. It used to drop the value without a word. It also
trims whitespace aroundallow_embed, as it already does for element text.validateSMIOptionschecksrequires_subscription,liveand
player_loc:allow_embedas well asfamily_friendly, and reports an invalid
value with the newInvalidVideoYesNoerror.SitemapAndIndexStreamerrors withERR_STREAM_PREMATURE_CLOSEinstead of
hanging when a sitemap's write stream is destroyed before it finishes, at any
point in the sitemap. ASitemapAndIndexStreamdestroyed during rotation no
longer opens another sitemap file once the current one has finished.SitemapAndIndexStreamdestroys itself with the error when a sitemap's write
stream fails while the sitemap is still open, such asEACCESorEISDIR
when opening the file. It used to crash the process with an unhandled
errorevent.simpleSitemapAndIndexnow rejects in that case.- Destroying a
SitemapAndIndexStreamalso destroys the open sitemap and its
write stream, so the file descriptor is released. SitemapAndIndexStreamdestroys the streamsgetSitemapStreamreturned when
it rejects the tuple, instead of leaving their file open.- At
ErrorLevel.THROW,SitemapAndIndexStreamfails when the index rejects a
sitemap's index item, such as a non-http(s) URL. It used to drop the error,
writing the sitemap file without listing it in the index. simpleSitemapAndIndexand the CLI connect each sitemap to its gzip and file
streams withpipeline(), so a gzip failure fails the sitemap instead of
leaving the write stream open.SitemapAndIndexStreamfails with the error, instead of leaving an unhandled
promise rejection, when writing the first item of a sitemap after rotation
throws.- At
ErrorLevel.THROW,SitemapIndexStreamno longer outputs a partial
<sitemap><loc>element before it fails on an invalidlastmod. simpleSitemapAndIndexand the CLI validate each sitemap URL before they
create its file, so a URL the index rejects no longer leaves an empty
sitemap file behind. They now fail on such a URL at every error level.sitemap --indexprints a stream error and exits with code 1 instead of
crashing with an unhandlederrorevent.sitemap --validateexits with code 1 when the sitemap is invalid and 2 when
validation cannot run (xmllint missing or not executable, or schema not
found). It used to exit 0 in every case, so scripts and CI could not detect a
failed validation. An xmllint that fails to start for a reason other than
ENOENT, such asEACCES, now rejectsxmlLint()with[error]alone
instead of[error, ''], so it is no longer reported as an invalid sitemap.sitemap --prependwrites every entry of the prepended sitemap, then the new
URLs. Both sources were piped into one stream, so whichever ended first
ended the sitemap: a large prepended file was cut off after its first entries
and failed with a write-after-end error.
A prepended file with more than 50,000 URLs, the most a sitemap may hold,
now fails with exit code 1 instead of being silently truncated.sitemap --parse,--prependand the default mode print a stream error,
such as a parse error or a missing input file, and exit with code 1 instead
of crashing with an unhandlederrorevent. In those modes a reader that
closes stdout early, such as| head, is not treated as an error. In
--indexmode it still is (exit code 1), because the sitemap files written
so far are left incomplete.xmlLint()andsitemap --validatefind the bundledschema/directory
when the package is installed as a dependency. The lookup searched relative
toprocess.cwd(), so outside this repository it threw a synchronous
"Schema directory not found" error that crashed the CLI. It now walks up from
the module's own directory, and a missing schema rejects the promise instead
of throwing.xmlLint()destroys aReadableinput if xmllint exits or fails to start
before reading all of it, so the source no longer stays paused with its file
descriptor open.SitemapStreamandSitemapIndexStreamcheck their publiclevelfield
when they warn, so changinglevelafter construction takes effect again,
as it did in 9.0.1.@types/nodeis a runtime dependency again, as it was in 9.0.1, because the
published type definitions import Node's stream types. The range now covers
every supported Node major (^22 || ^24 || ^26), so npm can share a
consumer's own copy.XMLToSitemapItemStreamnow treats CDATA sections as ordinary character data
in every tag. Previously only the 8 tags from issue #445 (loc,image:loc,
video:title,video:description,news:name,news:title,
image:caption,image:title) accepted CDATA; content in any other tag was
logged as unhandled. Seedocs/adr/0001-cdata-is-character-data.md.xmlLint()no longer probes for the binary withwhich, which is not a
command on Windows and made validation reportXMLLintUnavailablethere even
when xmllint was installed. A missing binary is now detected viaENOENTfrom
the spawn itself, which is correct on every platform.- The published tarball now contains only
dist/andschema/(via afiles
allowlist), so maintainer files such asCLAUDE.mdno longer ship to
consumers (#480). - The CLI locates
package.jsonby walking up from its own directory instead of
a hardcoded relative depth, so--versionno longer breaks when the build
output layout changes. sitemap --indexreports an invalid--limitwith the same message as
simpleSitemapAndIndex'sInvalidLimitError, prefixed with--limit:, and
accepts only decimal digits: forms such as1e3,0x10or250are
rejected rather than converted.InvalidLimitErrorsays the limit must be an integer between 1 and 50000,
rather than a number, since fractional limits are rejected too.XMLToSitemapItemStreamno longer adds an empty{ url: '', lang: '' }
entry tolinksfor anxhtml:linkthat lacksrelorhrefor has an
unsupportedrel. It still warns and records a parse error.XMLToSitemapItemStreamandXMLToSitemapIndexStreamcopy their options
instead of settingobjectModeon the object the caller passed in.
Documentation
api.mdnow documentsXMLToSitemapIndexStreamandparseSitemapIndex, and
the 50,000-entry and error-array caps the parsers enforce.api.mdno longer claimssimpleSitemapAndIndexaccepts an absolute
destinationDir; absolute paths have been rejected since 9.0.1 (#478).- JSDoc examples for
parseSitemapandparseSitemapIndexuseimportand
current APIs instead ofrequire()and the removedcreateSitemap.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Description
- Fixes #4286
- Supersedes and closes #4287
- This fixes cases where a user passes a link containing a search query or fragment hash in their sidebar config. Our link formatter would previously incorrectly include those as part of the URL pathname, instead of ensuring they are appended after any
.htmlextension or trailing slashes. - This PR incorporates @HiDeoo’s reviews from #4287 given OP was not responsive there.

Changes
- Fixes #18620
- The audit's
perf-use-image-componentandperf-use-videosrules read a loaded image's size from its Resource Timing entry (decodedBodySize) instead of fetching it again. - They still fetch when there is no entry, as for an image that hasn't loaded.
- In WebKit, fetching an animating SVG's URL froze its CSS animations, so Safari stopped them under
astro dev.
Testing
- New e2e test in
dev-toolbar-audits.test.ts: the audit flags a large<img>without a secondfetchof it. It fails without the fix. - The reproduction, checked in WebKit and Chromium: the ring now completes under
astro dev.
Docs
None: no user-facing behaviour changes beyond the fix.
Description
- Fixes #4317
- Supersedes and closes #4318
- This PR ensures that when table cells contain long words, these wrap onto new lines instead of overflowing when printing a page.
- I adapted the repro from #4317 to test some more cases and apply the fix: https://stackblitz.com/edit/github-rbvmtwhj?file=src%2Fstyles%2Fprint-fix.css

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| p-queue | ^9.3.5 → ^10.0.0 |
Release Notes
sindresorhus/p-queue (p-queue)
v10.0.0
Breaking
- Require Node.js 22
300a52d - The queue is now an
EventTargetinstead of anEventEmitter300a52d- Use
.addEventListener()and.removeEventListener()instead of.on(),.once(),.off(), and the otherEventEmittermethods. - The
completedanderrorevents have the result or the error inevent.detail. - An error thrown in an event listener now exits the process. Node.js reports it as an uncaught exception.
- Use
.clear()now rejects the promises of the removed tasks with anAbortErrorinstead of leaving them pending forever64311ff.clear()marks these promises as handled, but a promise made from them, like the one from.addAll()orqueue.add(fn).then(…), now rejects, so handle it.
TimeoutErroris now aDOMExceptionnamedTimeoutError, like the error ofAbortSignal.timeout()300a52d- Remove the deprecated
carryoverConcurrencyCountoption: usecarryoverIntervalCount300a52d - Stricter validation of options
76a48bad65d567concurrencyandintervalCapmust be integers (orInfinity). A limit of1.5used to let 2 tasks run.timeoutandintervalabove2147483647ms (the maximum timer delay) are rejected. They used to fire after 1 ms..add()rejects with aTypeErrorwhenpriorityisNaNor not a number.
.start(),.clear(), and settingconcurrencyno longer emitemptyandidlewhen the queue is already empty, soidleno longer fires on a queue that never had a taskaeedf53- A custom
queueClassmust now implementremove()300a52d
Improvements
- Zero dependencies!
300a52d - A task now runs in the async context of its
.add()call, so it sees theAsyncLocalStoragevalues of the caller, also when it starts later (Node.js 22.3 and later, Deno, and Bun) (#200)a5b7b54- Previously, a waiting task could see the values of whatever started it, like another request on a server.
- A task with a
timeoutnow gets asignalthat aborts when the task times out, so you can pass it on tofetch()and similar to stop the work300a52d .onEmpty()and theemptyevent now fire when the last waiting task starts, not when the next task finishes1cf5b82cb25a0a.addAll()now resolves with a typed tuple when the tasks return different types36e83aa
Fixes
- Fix many rate-limit bugs where
intervalCapwas exceeded at the end of a window, a waiting task got stuck, orisRateLimitedwas wrong6af55a71cf5b826c08a4fac89911450356a - Fix slow add, run, and abort for many tasks that share a signal, and
PriorityQueuekeeping finished tasks in memory95622a46fb8337 - Fix many edge cases with events and priorities, like infinite recursion in an
idlelistener and events in the wrong orderaeedf53b33dd448792846e79f970d65d5676f6028a - Fix
undefinedoptions and an invalid.timeoutsetter breaking the queued6cf96b48586f4 - Fix many TypeScript types
36e83aafa3c3e0
Migration guide
Events
-queue.on('completed', result => {
- console.log(result);
-});
+queue.addEventListener('completed', event => {
+ console.log(event.detail);
+});
-queue.once('idle', () => {});
+queue.addEventListener('idle', () => {}, {once: true});If the result or the error is undefined, event.detail is null, because CustomEvent works that way.
Other differences from EventEmitter:
- If you add the same listener twice, it is called once.
- A listener that is removed while an event is dispatched is not called for that event.
.clear()
The promises of the removed tasks now reject with an AbortError. If you await them, handle the rejection:
const results = await queue.addAll(tasks).catch(error => {
if (error.name === 'AbortError') {
return [];
}
throw error;
});Timeouts and signals
error instanceof TimeoutError still works. You can also check error.name === 'TimeoutError', which also matches the error of AbortSignal.timeout().
Other changes:
- The
TimeoutErrorstack trace no longer shows where the task was added. - With
timeoutset, the task'ssignalis no longer linked to yoursignalafter the task finishes. - Tasks with a
signalortimeoutsettle 2 microtasks later than before.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| muggle-string | ^0.4.1 → ^1.0.0 |
Release Notes
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| chokidar | ^5.0.0 → ^6.0.0 |
Release Notes
paulmillr/chokidar (chokidar)
v6.0.0
High-level changes
- Rewrote the watcher around a single observation pipeline. Backend callbacks are treated as invalidations and confirmed with
lstat,stat, orreaddirbefore any event is emitted, so the final state after a burst of changes matches the filesystem. - Added native recursive watching through
fs.watch({ recursive: true }). The defaultautobackend uses it on macOS and Windows and per-directory watching elsewhere. - Shared native handles across watchers and opened them per directory only: files no longer own handles. This fixes
EBADFerrors when watching many files on macOS (#1385, #1452). - Replaced
fs.watchFilewith Chokidar-owned stat polling. Poll loops are shared across watchers at the fastest requested interval. - Required Node.js 22.22 or later.
API changes
- Added the
backendoption:'auto'(default),'native','native-recursive', or'polling'.usePolling: trueremains as a deprecated alias forbackend: 'polling'.
- Renamed
intervalandbinaryIntervaltopollingIntervalandpollingBinaryInterval.- The old names remain as deprecated aliases; the new names win when both are given.
- Changed the
atomicdefault tofalsewith polling. An explicit value is preserved. - Made
close()terminal:add()now throws once closing has started. Construct a new watcher instead. - Validated options in the constructor: invalid
backend,atomic,depth,awaitWriteFinish, and polling intervals throwTypeError. - Emitted errors from
add()aserrorevents instead of unhandled rejections (#1378). - Made
getWatched()return a null-prototype object, so a watched directory named__proto__is listed (#1493). UseObject.hasOwn()instead ofhasOwnProperty()on the result. - Stopped applying
ignoredto directories above a path passed towatch()oradd(), so a missing path is still watched through its parent (#1374). Other entries in those directories are still filtered.
Fixes
- Fixed a 100% CPU loop when the process working directory containing a relatively watched file was deleted (#1474).
- Fixed watching a filesystem root, which emitted
unlinkandunlinkDirfor every entry (#1184, #452). - Fixed
UNKNOWNerrors fromfs.watchon macOS sockets, which prevented watching/var/run(#1391). - Fixed a symlink whose target passes through a regular file (
ENOTDIR) disabling watching of its directory and preventingready(#1476). - Fixed files created in a newly added directory between its scan and watch registration being missed (#1471).
- Fixed watching a missing nested path stopping its parent directory's subtree from being watched (#1470).
- Fixed false
changeevents on Windows when many sibling files are written (#1466). - Fixed duplicate
addevents for unchanged files under directory activity (#1465). - Fixed replacing a watched directory with a file of the same name hanging the process (#1464).
- Fixed persistent watching stopping after a watched directory was removed (#1463).
- Fixed a deleted watched path not being reported when recreated: previously only a deleted file that was the sole watched path was watched for its return. Any path passed to
watch()oradd()is now awaited from its nearest existing parent. - Fixed event throttling discarding updates; the newest differing change is now replayed when the window closes (#1455).
- Fixed relative
ignoredpaths; relative strings now resolve againstcwdor the process working directory (#1436). - Fixed files not being detected when their directory did not exist before watching (#1422).
- Fixed removed files being reported as
unlinkDirinstead ofunlink(#1421). - Fixed ignored files and directories still being watched in WSL (#1418).
- Fixed
changebeing reported for every file when one file changed under Deno (#1417). - Fixed changes not being detected after the second save (#1399).
- Fixed renaming a watched directory that contains subdirectories on Windows (#1380, #1398).
- Fixed re-watching a path not honoring
ignoreInitial(#1386). - Fixed
EISDIRerrors during the initial scan of network drives (#1376). - Fixed watching an array of absolute file paths (#1366).
- Fixed unwatching a deleted watched directory on Windows, contributed by @sapphi-red in pull request #1467.
- Documented that unwatched paths stay ignored until they are added again (#1439).
Misc
- Made the
Statsimport type-only, contributed by @zhennann in pull request #1447. - Pinned dev dependencies and restricted workflow permissions, contributed by @43081j in pull requests #1457, #1460, and #1461.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.

Changes
- Replaces
yargs-parserwithmrifor Astro CLI argument parsing while preserving existing option handling. Recommended by e18e - Leaves
@astrojs/checkon its existing parser and dependency.
Testing
- Adds parser contract coverage for positionals, aliases, negated flags, optional and repeated values, unknown options, and the
--delimiter.
Docs
Changeset
AI was used to help implement this change.
Description
This PR tweaks some of our workflows to reduce the number of unnecessary CI workflow runs triggered by Changesets release PRs.
Sharing a diagram of the new approach to make it easier to follow if needed:
flowchart LR
A["PR merged to main"] --> B["Draft release PR created or updated"]
B --> C["CI skipped"]
C --> D["Maintainer marks release PR as ready for review"]
D --> E["CI runs once"]
E --> F{"Another PR merged to main?"}
F -- "Yes (back to draft)" --> B
F -- "No" --> G["Release PR merged"]
When a Changesets release PR is opened, every merge to the main branch updates it and triggers CI workflows on the release branch. These runs do not provide a lot of value as they run in parallel with the ones we already run on the main branch on slightly different content (package.json files updates, lockfile changes, and Markdown changes for the changelogs).
The idea is to not automatically run CI workflows for Changesets release PRs until we are ready to release as a last verification step. In the Starlight repository, the impact should be moderate but it's a good test bed for this approach to see if we could use something similar in a few other repos where some workflows take a long time to run and count heavily against our org runner limits.
These workflows are automatically started because the changesets/action action does not use the default GITHUB_TOKEN token. When the default GITHUB_TOKEN is used, GitHub automatically puts triggered workflows in an approval-required state. Unfortunately, this is more of a behavior than a feature as I could not find any documented way to say "if ... then put this workflow in an approval-required state".
I experimented with various approaches to implement this behavior in a private repo, e.g. an environment with required reviewers to gate workflow runs, but this PR ends up using an approach that sounds simpler to me as everything happens in the PR page itself and only involves a well-known feature: draft PRs.
In practice, Changesets release PRs are now created (and updated) as draft PRs. We use this state to prevent some CI workflows from running automatically, and when we are ready to release, a maintainer can mark the PR as ready for review, which will then trigger all expected CI workflows. As draft PRs cannot be merged, this also prevents merging an untested release PR.
If a PR is merged to main while the release PR is already ready for review, the release PR is updated and converted back to a draft and needs to be marked as ready for review again.

Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
Release Notes
withastro/compiler-rs (@astrojs/astro2tsx)
v0.1.3
Patch Changes
-
266acf4: Fixes an issue where processing instructions weren't correctly parsed, resulting in an error. Now the following code is correctly transformed:<?xml version="1.0" encoding="UTF-8"?> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 10 10" {...Astro.props}> <circle cx="5" cy="5" r="4" /> </svg>
-
089b077: Updates Astro’soxcfork to the latest commit
withastro/compiler-rs (@astrojs/compiler-rs)
v0.5.2
Patch Changes
withastro/astro (@astrojs/language-server)
v2.17.3
Patch Changes
- #18460
044148dThanks @Princesseuh! - Speeds upastro checkby skipping a 10 ms editor-cancellation wait that ran before checking each file
babel/babel (@babel/core)
v8.0.10
🐛 Bug Fix
babel-parser- #18420 fix(parser): improve radix literal rounding (@JLHwung)
- #18372 fix(parser): allow parenthesized assignment target in arrow initializer (@JLHwung)
- #18410 fix(parser): do not record strict mode errors during lookahead (@JLHwung)
- #18433 fix(parser): invalid expectOnePlugin usage (@JLHwung)
- #18409 fix(parser): handle ASI after let followed by a reserved word on the next line (@JLHwung)
- #18406 fix(parser): parser should not crash for
import defer {}(@JLHwung) - #18407 fix(parser): record start location in
startNodeAt(@JLHwung)
babel-plugin-transform-block-scoping- #18371 fix: closures in for-loop test and update capture wrong binding (@joellemd)
babel-generator- #18418 fix(generator): keep aliases of string-literal module specifiers (@JLHwung)
- #18427 Fix missing parentheses around TypeScript assertion targets (@dagemawinegash)
- #18324 fix: invalid
minified: trueoutput for new expression (@JLHwung) - #18437 fix(generator): preserve type modifier in TSImportEqualsDeclaration (@saiyam-jain-dev)
- #18424 Keep parentheses around TSInstantiationExpression operand (@yulman2207)
- #18417 fix(generator): do not disallow line break after import source (@JLHwung)
babel-plugin-transform-optional-chaining,babel-traversebabel-helper-create-class-features-plugin,babel-plugin-proposal-decorators- #18224 fix: avoid removable fields as decorator evaluation hosts (@nyan-left)
babel-typesbabel-plugin-transform-classes- #18384 Leave loose class prototype mutable with accessors (@nicolo-ribaudo)
🏠 Internal
babel-build-external-helpers,babel-core,babel-helpers,babel-plugin-transform-async-generator-functions,babel-plugin-transform-class-properties,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-regenerator,babel-runtime-corejs3,babel-runtime- #18397 Mangle top level names in helpers (@nicolo-ribaudo)
🏃♀️ Performance
🔬 Output optimization
v8.0.9
v8.0.9 (2026-10-23)
This release contains no changes. It is needed only to update the repo (which is based on @babel/core's last release) in Node.js's CITGM.
cloudflare/workers-sdk (@cloudflare/vite-plugin)
v1.66.0
Minor Changes
-
#16539
046db08Thanks @petebacondarwin! - Update the development registry to use the canonical Cloudflare pathUpgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses
CLOUDFLARE_DEV_REGISTRY_PATHor<Cloudflare config directory>/dev-registry/v5for Worker discovery.MINIFLARE_REGISTRY_PATHis no longer read. When mixing Vite and Wrangler development sessions, set the sameCLOUDFLARE_DEV_REGISTRY_PATHfor both because Wrangler retains its legacy default. -
#16407
9ec1101Thanks @petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and previewSet
remote: trueon a Hyperdrive binding inwrangler.jsoncto connect to its deployed configuration without a local database connection string. The retained remote proxy exposes the binding's connection string and socket streams, and remote session cleanup preserves startup errors and shares one disposal attempt.
Patch Changes
-
#16542
ef573d4Thanks @petebacondarwin! - Preserve machine-readable error properties from remote bindingsEnable enhanced error serialization on the remote proxy Worker used by Vite plugin v1. Combined with Miniflare 5.20261023.1-beta, remote binding errors retain properties such as
codeandnumericCodeso Worker code can handle them without parsing error messages. -
#16480
ccaa34aThanks @petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startupUpdate the Undici dependency bundled from the retained remote-bindings package to
7.30.1. Responses with excessive content encodings now reject without a later unhandled stream error when the server closes the connection early. -
#16502
6f2eda1Thanks @petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6The Vite plugin validates
_headersand_redirectsthrough its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections. -
#16444
79678c4Thanks @petebacondarwin! - Update Vite plugin v1 to the October 23 Workers runtimeUse Miniflare
5.20261023.0-betaand the matching Wrangler release for local development and preview. Align bundled helpers and Workers types with this runtime, and use2026-10-23as the fallback compatibility date when none is configured. The runtime and helper updates also prevent malformed HTTP responses with excessive content encodings from causing unhandled stream errors. The published helpers also update their bundled Zod validator a
[!IMPORTANT]
✂ PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/starlight@0.42.9
Patch Changes
-
#4218
effea21Thanks @delucis! - Reduces install size by ~400 KB by switching the YAML parser used internally for projects using Astro 7.3.6 or later -
#4316
8679b1cThanks @clean99! - Fixes localized routes and language switcher links for pages in directories named likeObject.prototypeproperties, such asconstructor. -
#4341
e1ac1b4Thanks @delucis! - Prevents tables overflowing and clipping when printing a page

Which issue does this PR close?
Fixes #18606
Rationale for this change
With security.csp enabled, Astro adds the <meta http-equiv="content-security-policy"> element using a placeholder emitted inside renderHead() at the end of <head>. A <meta> CSP policy only applies to content parsed after it per the W3C CSP specification. As a result, scripts declared in <head> (e.g. is:inline scripts, analytics snippets, and injected scripts) run outside the policy and are not covered.
What changes are included in this PR?
- In
packages/astro/src/runtime/server/render/page.ts:- Updated
replaceCspMetaPlaceholder()to remove the placeholder from the tail of<head>and insert the rendered CSP<meta>tag at the start of<head>. - Places the tag immediately after
<meta ... charset=...>so character encoding declarations stay within the first 1024 bytes of the document (HTML spec compliant). If no<meta charset>is found, places it right after the<head>opening tag. - If no
<head>tag is present, falls back to replacing the placeholder in-place.
- Updated
- In
packages/astro/test/units/csp/rendering.test.ts:- Added unit test verifying that the CSP
<meta>is placed after<meta charset>and before head scripts in non-streaming renders. - Added unit test verifying that the CSP
<meta>is placed at the start of<head>when<meta charset>is absent.
- Added unit test verifying that the CSP
- Added changeset (
astro: patch).
Are these changes tested?
Yes:
- Unit tests: Added 2 new tests in
packages/astro/test/units/csp/rendering.test.ts(all 30/30 CSP rendering tests passing, all 84/84 CSP tests passing). - Type checking:
pnpm run test:typespassed with 0 errors. - Formatting:
pnpm biome checkpassed with 0 errors.

Part of the composable Vite plugins RFC. Fourth PR of the stack: framework islands in a plain Vite project.
Changes
- Adds
@astrojs/react-renderer,@astrojs/preact-renderer,@astrojs/solid-js-renderer,@astrojs/svelte-rendererand@astrojs/vue-rendererunderpackages/renderers/. Each exports its renderer as plain data, forastro({ renderers: [react()] })next to the framework's own Vite plugin, and has no dependency onastro, so a Vite project doesn't install the CLI. The renderer code is moved (not copied) from the integrations, in a renames-only commit. @astrojs/react,@astrojs/preact,@astrojs/solid-js,@astrojs/svelteand@astrojs/vuedepend on their renderer package and register it alongside the framework's Vite plugin. Their public paths (./server.js,./client.js,./container-renderer, …) re-export the renderer package, so options and output are unchanged.reexportRenderer()in@astrojs/internal-helpers/rendererpoints a renderer's module ids at the integration's re-exports, since an Astro project depends on the integration and may not be able to resolve the renderer package (pnpm doesn't hoist it).- Adds
examples/vite-plugin-astro-hono: a Hono app that renders an Astro component with a React island usingrenderToResponse().
Testing
- A frameworks fixture with an island per framework, server-rendered and hydrated in dev and in a build.
- Renderer tests in each renderer package, moved from the integrations; the standalone fixture uses
react(). - The existing integration and
astroframework tests cover the integrations.
Docs
- The renderer packages are covered by the guide in withastro/docs#14831.

Part of the composable Vite plugins RFC. Third PR of the stack: Astro components rendered from any server in a plain Vite project.
Changes
astro()works without the Astro CLI: add it to a Vite config, import.astrofiles from server code, and render them withrenderToString()orrenderToResponse()from@astrojs/runtime.- Styles, scripts and islands are collected per component tree: from the module graph in dev, and in a build from the server environments, which decide the client build entries. The rendered HTML links to the built assets.
- Compiled components register the plugin's config with the runtime (
virtual:astro:render-setup), so the render functions need no manifest.createRenderer()renders components without Vite; rendering before any compiled component is loaded throwsRenderNotConfigured. - Renderers are plain data with declarative fields (
options,optimizeDeps,dedupe,noExternal,devHeadScript,appEntrypoint) thatastro()applies; the framework's own Vite plugin compiles its files. - Drops the
srcDiroption ofastro(). A root-relative<script src>now errors only when it points to a file inpublicDir, so project files outsidesrc/are bundled.
Testing
vite-plugin-astrotests for options, the plugin API and the CLI argument, rendering in dev (styles, islands, style HMR, markup reloads) and in a build (linked stylesheets, client chunks), and the public<script src>check, with a standalone fixture.runtimetests forrenderToString,renderToResponseandcreateRenderer.
Docs
- A guide for using Astro components in a Vite project is drafted in withastro/docs (
docs/vite-plugin-astro).

Part of the composable Vite plugins RFC. Second PR of the stack: makes the moved code work where it now lives, with no behavior change.
Changes
- Adds the
@astrojs/runtimeand@astrojs/vite-plugin-astropackages (manifests, tsconfigs, READMEs) around the moved code, rewrites imports, and narrows the moved files' config types (CompileConfiginstead ofAstroSettings). astro(options, cli)from@astrojs/vite-plugin-astroserves the compile, renderer, script, head and HMR plugins.createVite()calls it once; plugins only the CLI uses stay inastro.- The
astro/*paths of moved modules stay as re-exports, and the Astro config schema is built from the plugin's option schemas, so config validation and defaults are unchanged. - Modules that other packages import live under
src/internal/and are exported as@astrojs/runtime/_internal/*and@astrojs/vite-plugin-astro/_internal/*(mapped todist/internal/*). These are for use within the monorepo only, with no stability guarantees.
Testing
- No new tests: behavior is unchanged, and the existing
astrounit and integration suites cover it.
Docs
- No docs update needed: nothing user-facing changes.

Part of the composable Vite plugins RFC. First PR of a stack: this one only moves files.
Changes
- Moves Astro's render runtime to
packages/runtime(server rendering, client directive scripts, JSX and compiler runtimes, head propagation, errors and error data, encryption, view transitions) and the.astrocompiler and syntax-layer Vite plugins topackages/vite-plugin-astro. - Pure
git mv: 92 renames, no content changes (git diff -M100% --summaryshows only renames). The old paths are removed here and come back as re-exports in the next PR. - Does not build on its own; the next PR wires the moved code up.
Testing
- None in this PR: it only moves files. The next PR is the first one that builds and runs the existing suites.
Docs
- No docs change for the move itself. The docs repo's error reference script reads
errors-data.tsfrom its old path, so the Smoke job fails until that script is updated.

Fixes #18568
attachDataStoreInvalidation always called invalidateDataStore with notifyClient: true. In astro dev, the initial content-layer sync writes the data store before the server is listening. Vite buffers that full-reload and delivers it right after the first client connected, so the first page loads twice on a fresh start.
dev() now passes a shouldNotifyClient callback that returns false while the initial sync runs. Server-side invalidation still happens. sync() awaits waitUntilSaveComplete(), so the startup write finishes before the flag flips. Writes after startup still reload, including ones Vite buffers for a temporarily disconnected browser. This mirrors buildStart, which already skips the client notify (#17286).
Test plan
- Unit: a write during initial sync invalidates the server but sends no client
full-reload. A later write does reload. - Existing invalidation, watcher-echo and prerender tests still pass
Description
- Closes #4336
<site-search>(Pagefind) and<sl-doc-search>(@astrojs/starlight-docsearch) only initialized in aDOMContentLoadedlistener, so if their script ran after that event, search never set up. The listener was left over from when Pagefind loaded via an inline script; module scripts already run after parsing, so both components now initialize directly in their constructors.- Starlight's default output is unaffected in practice: its module scripts run before
DOMContentLoaded, and Pagefind setup still waits forrequestIdleCallback. This matters when page scripts are added dynamically, for example on a static site using a CSP with'strict-dynamic'and no nonces (see withastro/astro#18607).
Important
The DocSearch change isn't tested in a browser because it requires an Algolia setup (which I don't have). The Pagefind change is verified in the reproduction.

Changes
- Negation patterns like
!_docsnow correctly exclude files inside that folder during dev server reloads, matching the behavior of the initial sync via tinyglobby. Previously, the watcher's picomatchignorecheck only tested a file's own path, so_docs/x.mdwasn't caught by!_docs, causing excluded files to be added to the collection on edit. - Each negation is now passed to picomatch's
ignorelist both as written and with/**appended, so a negation that matches a folder also excludes all files inside it.
Testing
- Added a unit test in
packages/astro/test/units/content-layer/glob-loader.test.tscovering the watcher filter with folder-level negation patterns (!_docs,!_doc*,!**/_docs). The test fails before the fix and passes after.
Docs
- No docs update needed; this restores already-documented behavior for negation patterns in the glob loader.
Closes #18590

Changes
envField.number()parses the value withNumber.parseFloat(), which stops at the first character that isn't part of a number. Soabcis rejected, but8080abc,10pxor1,5pass validation as8080,10and1. The last one is easy to hit with a decimal comma, and the wrong value is used silently.- The validator now uses
Number(), which only accepts the whole string as a number, and rejects blank values first, sinceNumber('')is0. Valid values such as42,4.5,-1or1e3parse the same as before. (Number()also reads0x10as 16, whereparseFloat()gave 0.) - Changeset added (
astropatch).
Testing
Added a case to packages/astro/test/units/env/env-validators.test.ts that checks 8080abc, 1,5, 10px, an empty string and a blank string are all rejected with a type error. It fails on main (8080abc validates as ok) and passes with the fix. The rest of test/units/env/ and test/env-secret.test.ts / test/env-public.test.ts still pass.
Docs
No docs change. The docs don't describe the lenient parsing, and invalid numbers are already reported as a type error.
I used Claude Code to write this change.

Changes
- Group all minor and patch dependency updates into one Renovate PR while keeping major updates separate (see current jobs list at https://developer.mend.io/github/withastro/astro, there are dozens entries). This reduces routine PR volume and makes dependency reviews easier to manage.
- Made with AI.
Testing
N/A
Docs
N/A

Changes
astro checknow flushes all buffered stdout/stderr output before the process exits. Previously,process.exit()was called synchronously aftercheck()resolved, which silently dropped any data the pipe reader hadn't consumed yet — causing truncated output and a missingResultsummary in CI wrappers reading from a slow pipe.- A new
flushAndExit(code)helper inpackages/astro/src/cli/flush-and-exit.tswrites an empty chunk with a callback to each stream and defersprocess.exit(code)until both callbacks fire. A companionignoreEpipe()helper registers a no-op'error'listener on stdout and stderr beforecheck()runs, so early-closing readers (e.g.| head) exit cleanly instead of crashing with an unhandledEPIPEerror.
Testing
packages/astro/test/units/cli/check.test.tswas added, covering the full-flush path (all bytes delivered to a slow reader), correct exit codes for error and no-error projects, and clean exit when the reader closes early.
Docs
- No docs update needed; this is an internal CLI reliability fix with no user-facing API change.
Closes #18600

Changes
- The two failing font E2E tests hard-coded
roboto@latestURLs; the Fontsource API now returns versioned URLs (e.g.roboto@5.3.0/...), causing both URL assertions and the font file IDs hashed from those URLs to no longer match. - Adds a
getFontsourceFile()helper in the test file that locates each remote Roboto file by ID prefix and validates its URL against aroboto@[^/]+/<file>pattern, making assertions version-agnostic without relaxing any other checks (family hashes, unicode ranges, fallback metrics).
Testing
- Updated the two previously failing tests in
packages/astro/test/units/assets/fonts/e2e.test.tsto use the new helper instead of hard-coded@latestURLs and file IDs, covering version-independent URL matching.
Docs
- No docs update needed; this is a test-only change with no user-facing behavior impact.
Closes #18598
Description
- Closes #4331
- When the X or Twitter link in the
socialconfig ends with a slash, for examplehttps://x.com/astrodotbuild/, Starlight renders<meta name="twitter:site" content="@astrodotbuild/">, which is not a valid handle. - This PR strips both the leading and trailing slashes from the link pathname, so the tag is
@astrodotbuildwith or without the slash. - Adds a unit test with a trailing-slash
x.comsocial link, and a changeset. - No visual change.

Part of the implementation of the enhanced content collections RFC (collection metadata).
Changes
- MDX entries and
deferRenderMarkdown entries are compiled as modules after sync, so sync writes.astro/collection-files.json, mapping their files to their collection. A newastro:collection-filesVite plugin exposes the lookup through itsapi, used by@astrojs/mdxand Astro's Markdown plugin. - A file loaded by more than one collection is compiled once for all of them, so its collection is left
undefined. COLLECTION_FILES_PLUGIN_NAMEandCollectionFilesApilive in@astrojs/internal-helpers/collections, shared by astro and@astrojs/mdx. The MDX plugin looks the collection up by file: entries and direct imports of a file share its compiled module.- In development, the map is also written after loader changes outside syncs, and modules whose collection changes are invalidated and compiled again.
Testing
- Unit test for the file to collection map, including files shared by collections.
mdx-collection-metadata.test.tsbuilds MDX and deferred Markdown entries and a shared file, and checks in dev that editing descriptors recompiles the MDX page.
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection metadata).
Changes
- Markdown plugins receive the metadata of the collection being rendered as
file.data.astro.collection(ctx.data.astro.collectionin Sätteri), for entries rendered byglob()and byrenderMarkdown()in custom loaders. - Moves
AnyCollectionMetadataandJSONValueto a new@astrojs/internal-helpers/collectionsexport, re-exported byastro, so the Markdown processors don't depend onastro. - Adds an optional
collectiontoMarkdownRenderOptions, an optional fourth argument toMdxRenderer.process(), and an optional second argument toContentEntryRenderFunction. Processors and entry types that ignore them keep working.
Testing
- remark and Sätteri
collection.test.tscover Markdown and MDX processors. - The astro
collection-metadatafixture rendersglob()andrenderMarkdown()entries through a remark plugin, with the flag on and off.
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection metadata).
Changes
- Adds the
astro:collections:resolvedintegration hook, called with the metadata of the build-time collections before any loader runs, and again in development only when the content config changes. Requiresexperimental.collectionMetadata. - Live collections aren't included, because
live.config.tsisn't loaded during sync. - The hook is called during the content sync, after
astro:config:doneand before any loader runs. Inastro build, it runs on every build beforeastro:build:start, so before the build's Vite pipeline loads any module, except the modulescontent.config.tsimports. Inastro dev, it runs afterastro:server:setupand beforeastro:server:start. The hook's JSDoc documents this order.
Testing
- Unit tests check the hook is called once per content config with the metadata, and not called when the flag is off.
collection-metadata.test.tschecks the order in a build:astro:config:done,astro:collections:resolved,astro:build:start, then the first module the build's Vite pipeline loads.
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection metadata).
Changes
- Adds the
experimental.collectionMetadataflag andgetCollectionsMetadata()inastro:content: every build-time then live collection, as{ name, type, loader: { name }, descriptors }, without loading entries. It throwsCollectionMetadataNotEnabledwhen the flag is off. - Adds
descriptorson loaders (build-time and live),defineCollection()anddefineLiveCollection(). The collection's values override the loader's. They are ignored when the flag is off, so libraries can set them on their loaders unconditionally. - With the flag off, descriptors are ignored and not checked at all, so a library can set them whether or not its users enable the flag. A dedicated fixture checks that a descriptors value that isn't an object doesn't fail the content config without the flag.
LoaderandLiveLoadertake aTDescriptorsgeneric, anddefineCollection()/defineLiveCollection()keep the literal types of theirdescriptors. The generatedCollectionMetadatatype is a union with one member per collection, whosedescriptorsmerge the loader's and the config's types, so editors autocomplete them. An index signature lets code read a key on every collection, including those that don't set it.- Adds the
CollectionMetadataWith<D, T>type inastro:content, which narrowsCollectionMetadatato the collections with the descriptorsD, and optionally the typeT, for use in type guards. - Names the general shape
AnyCollectionMetadatainastro, for code outside a project, like integrations and Markdown plugins, which can't see its generated types.CollectionMetadatais only the generated type ofastro:content, so the two no longer share a name. - Build-time metadata is written at the start of each sync to
.astro/collections-metadata.jsonand served by anastro:collections-metadatamodule; live metadata is computed at runtime fromlive.config.ts.
Testing
collection-metadata.test.ts(unit) covers descriptor merging, inline loaders, writing and removing the file, and the generated module.collection-metadata.test.ts(integration) builds a fixture with build-time, inline and live collections, checks lookup by descriptor, that results are copies, and the flag-off error.test/types/collection-descriptors.tschecks thatExtractCollectionMetadata, whichCollectionMetadataWithuses, narrows by descriptors and by type.
Docs
- No docs yet: docs will come with the experimental flag page.

Changes
- Implements roadmap#1458: on a cache miss, the memory cache provider (
memoryCache()) returns the response as it renders and stores a copy when the body completes, instead of reading the whole body before the first byte. The stored entry is unchanged; a body that fails mid-stream is logged and not stored. - The store is passed to
waitUntilwhen the adapter provides one, so serverless runtimes keep it alive after the response is sent. WithoutwaitUntil(e.g. Node) it completes on its own. - As on an uncached page, a render error once the page has started streaming ends the response instead of rendering the 500 page.
Testing
- Why existing tests changed: a miss is now stored after
onRequestreturns, so a test that checks the cache straight after a miss races the store. An expected HIT fails, and an expected MISS (different host, Set-Cookie) passes whether or not the entry was keyed correctly. Tests now record the store through awaitUntilthey pass in and await it before those checks, using a newtest/units/cache/test-helpers.ts; the helpers fail after 1s instead of hanging.app-cachepasses the hook toapp.render, and the test adapter forwards it socache-memory-querycan too; that file's helper also fails if no store was recorded. - New
memory-provider streaming misstests fake a slow render with a body that sends<head>and holds</html>until the test releases it:- the miss response returns and streams
<head>while the body is held, then the full page is stored, with and withoutwaitUntil; on a provider that waits for the body,onRequestfails a 1s guard instead of hanging; - a visitor who cancels mid-stream still leaves the full page stored;
- a body that errors mid-stream logs one warning and stores nothing, with and without
waitUntil; without it, a store that didn't catch its own failure would be an unhandled rejection.
- the miss response returns and streams
Docs
No docs update needed: there is no API or configuration change.
🤖 Generated with Claude Code

Changes
astro checknow exits with code 1 when@astrojs/checkortypescriptcannot be loaded (e.g. in CI where packages can't be auto-installed). Previously, the missing-packages branch did a barereturn;, which resolved toundefinedand caused the CLI to callprocess.exit(0), silently passing CI even though no type-checking ran.- Changed
return;toreturn true;inpackages/astro/src/cli/check/index.ts, matching the existing behavior of the TypeScript 7 incompatibility branch added in #18053.
Testing
- Adds a unit test in
packages/astro/test/units/cli/check.test.tscovering the case wheregetPackage()returnsundefinedfor@astrojs/checkortypescript, asserting thatcheck()returnstrue(triggering exit code 1).
Docs
- No docs update needed; this is a bug fix restoring the expected exit-code contract with no API or configuration changes.
Closes #18588

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.
Releases
@astrojs/cloudflare@15.0.0-beta.5
Patch Changes
- #18553
bf39bf6Thanks @petebacondarwin! - Updates the Cloudflare adapter to use the Vite plugin's full configuration API while preserving user-defined Worker settings, bindings, and Containers
Description
This PR is a follow-up to #4175:
- Adds the SHA for the #4175 commit to
.git-blame-ignore-revsso it doesn’t show in git blame. - Removes two files from our
.prettierignorefile as these can now be successfully formatted with the updated plugin. (@HiDeoo suggested this in a review but I forgot to apply it there.) - Runs formatting for those two files.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- Adds
createStorageDriverTests()atastro/content/storage-driver-tests: the tests a driver must pass, independent of any test runner.
Testing
- Runs the suite against the in-memory test driver, and checks that it fails for a driver that ignores the snapshot ID.
- The SQLite driver tests use the suite instead of their own copies.
- The suite also checks that writing a snapshot again in development replaces its entries, and, when the driver implements them,
listSnapshots()anddeleteSnapshot().
Docs
- No docs yet. The changesets are in #18632, the last PR of the stack.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@7.4.6
Patch Changes
-
#18565
cd09986Thanks @praveen-kumary! - Avoids attributing client-only components or scripts to unrelated pages importingastro:i18nby bounding top-level page graph traversal at virtual page entries -
#18608
babd96dThanks @umeraamir69! - Fixes an extra page reload on the first page load after startingastro devwithout an existing.astrodirectory -
#18589
402c0faThanks @astro-factory! - Fixesastro checkexiting with code 0 when@astrojs/checkortypescriptis not installed. The command now exits with code 1 so CI fails instead of silently skipping type checking. -
#18503
54fcdd5Thanks @SwastikTripathi! - Preserves the last-modified date of cached font files and unchanged public files when copying them into the build output. Public-file timestamp preservation respects the resolved public-directory configuration, follows source symlinks, and avoids backdating files overwritten by build plugins. -
#18605
76cd239Thanks @astro-factory! - Fixes theglob()loader adding files from a folder excluded with a negation pattern such as!_docswhen they change duringastro dev -
#18432
ed60d82Thanks @alexmv! - Improves theMissingSharperror to include the reason Sharp failed to load, such as its prebuilt binaries not supporting the current CPU -
#18474
59543c3Thanks @miottid! - Fixes i18n fallback for on-demand rendered pages. A locale-prefixed request for a page that only exists in the fallback locale (for example/de/aboutwithfallback: { de: 'en' }) was answered with status302and noLocationheader. Such requests are now rewritten or redirected to the fallback locale according toi18n.routing.fallbackType, including encoded paths and sites with a configuredbase. Query strings are preserved, and explicit page statuses and redirects are left unchanged. -
#18541
cfa2d2bThanks @ump45nose! - FixesmatchAllRoutesto considerfallbackRoutes, matchingmatchRouteand the production router. Dev-server i18n fallback requests now resolve to the source route's metadata instead of the 404 route, and SSR-only fallback candidates can fall through the prerender handler. -
#18602
d856064Thanks @astro-factory! - Fixesastro checklosing the end of its output, including theResultsummary, when stdout is piped to a slow reader. When the reader closes the pipe early, for exampleastro check | head,astro checknow exits with code 1 instead of crashing with anEPIPEstack trace. -
#18574
da0f149Thanks @astro-factory! - Fixes an unnecessary full page reload inastro devwhen a content loader callsstore.clear()orstore.delete()and the content store has no asset imports -
#18570
e71c038Thanks @astro-factory! - Fixes pages using<ClientRouter />briefly showing the top of the page on reload before jumping back to the previous scroll position. Full reloads now use the browser's native scroll restoration. -
#18531
f75553bThanks @praveen-kumary! - Fixes an unhandledTypeError: Cannot convert undefined or null to objectwhen callingroute.generate()without arguments on static routes
@astrojs/cloudflare@14.4.5
Patch Changes
- #18562
9055de2Thanks @astro-factory! - Fixes the passthrough/_imageendpoint returning a 404 instead of304 Not Modifiedwhen the browser revalidates a cached local image withIf-None-Match. Revalidation supports weak ETags, tag lists, and wildcard conditions for local and allowed remote images while preserving image-type validation. - Updated dependencies []:
- @astrojs/underscore-redirects@1.0.4
@astrojs/node@11.1.10
Patch Changes
- #18563
8a92f7cThanks @astro-factory! - Fixes on-demand routes receiving an empty request body on Node.js 26 whenstaticHeadersis enabled
@astrojs/react@7.1.3
Patch Changes
- #18535
b21d724Thanks @praveen-kumary! - Preserves component-rendered resource links, including stylesheets, preloads, and modulepreloads, in React island output. Automatic React resource hints are also preserved so that authored links are not removed during server rendering.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- Adds
@astrojs/collection-storage-sqlite:sqlite({ url, authTokenEnv })keeps collections in a local SQLite file or a remote libSQL database such as Turso. - Snapshots share two tables. A snapshot is listed in the snapshots table only once committed, so a reader can't open an uncommitted one. Entries are written and read in pages.
- Implements
listSnapshots()anddeleteSnapshot(), which deletes a snapshot's entries and row in one transaction. The snapshots table recordsdev, and opening a writer clears the snapshot's entries, so a dev server can write its snapshot again. - The auth token is read with
getSecret()fromastro:env/server, from the variable named byauthTokenEnv, never passed as an option. It can come from a.envfile at build time, and is never written into the build. @libsql/clientis a peer dependency: it must be a direct dependency of the project, so the server build keeps it external and libSQL can load its native binding.sqlite()points at the driver file with a file URL. The package doesn't ship a web version: the driver runs in Node only, and runtimes such as Cloudflare Workers are expected to use their own driver, e.g. a D1 driver shipped by the adapter.
Testing
driver.test.tscovers the descriptor, uncommitted snapshots and config errors.fixture.test.tsbuilds a site whose collection is stored in SQLite.
Docs
- The package has a README. Docs will come with the experimental flag page.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- In
astro dev, collections withstorageare read through their driver too, so driver problems show up during development. - Development has a single snapshot: every dev server, in every session, writes the snapshot
dev, again after each sync and each store write that loaders make outside of syncs.createSnapshotId()isn't called, as it may return the ID of a deployment. Writing.astro/collection-storage.jsoninvalidates the bundled drivers module, so readers reopen. - Dev restarts sync through
syncInternal(), which passesdev: trueforcommand: 'dev', so a restart writes thedevsnapshot too.
Testing
- Adds a dev server suite to
collection-storage.test.ts: it reads a stored entry, edits its file, and checks that the page updates from the same snapshot. collection-storage-sync.test.tschecks that dev servers write to the snapshotdev, withdev: true, without callingcreateSnapshotId().
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- A new
astro:collection-storagemodule bundles the drivers and the snapshot each one must read.getCollection()andgetEntry()read those collections through a reader per driver, created on first use. getEntry()andgetEntries()accept{ content: false }, andgetCollection()accepts it in a query object,getCollection({ name, filter?, content? }), so the filter doesn't have to beundefined. Entries are returned withoutbodyandrendered, with matching types. It works for bundled collections too.render()throwsRenderEntryWithoutContentErrorfor those entries.- The
contentoption requiresexperimental.collectionStorageDrivers: with the flag off, the read functions throwContentOptionNotEnabled, and the generated types only acceptcontentwhenastro syncsees the flag on. - Trims the internal
DataStoreSourceinterface to the three methods the runtime uses.
Testing
collection-storage-runtime.test.tscovers the stored, in-memory and composite sources, and the generated module.collection-storage.test.tsbuilds a fixture with a JSON file driver: prerendered pages, an on-demand endpoint using every read function, no stored entries in the server bundle, and a new snapshot per build.- The fixture also stores a collection with
deferRenderentries, sharing the driver ofdocs, and an image field, and a second fixture checks the error and the types with the flag off.
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- At the end of each sync, collections with
storageare written to a new snapshot of their driver and committed. Collections sharing a descriptor share a driver and a snapshot. Loaders are unchanged: they still write to the in-memory store. astro syncandastro checkwrite no snapshot (writesStoredCollections: false): nothing would read it, as builds and dev servers write their own. They also don't load drivers, so generating types never connects to a remote database.- The snapshots are recorded in
.astro/collection-storage.json, and those collections are left out of the bundled data store module. They stay in the cached data store, so loaders keep their incremental state. - Drivers are imported once per descriptor, through the Vite runner that loads the content config (
createViteDriverLoader()), wired into sync, dev and dev restarts. Entrypoints resolve from the project root, and drivers can import virtual modules such asastro:env/server, as they do once bundled with the server. Entrypoints are normalized bynormalizeEntrypoint(), moved out of the logger along withimportEntrypoint(), which stays the default import function. Invalid entrypoints throwInvalidCollectionStorageDriver.
Testing
- Adds an in-memory test driver to the content layer test helpers.
collection-storage-sync.test.tscovers snapshot grouping and IDs, driver loading errors, the content layer writing and removing the record, and the exclusion from single-file and chunked bundled stores. It also checks that a content layer that doesn't write stored collections loads no driver.
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- Adds the public
CollectionStorageDrivercontract: an optionalcreateSnapshotId(),openWriter({ snapshot, dev })withwrite()/commit(),openReader({ snapshot })withget()/entries(), and optionallistSnapshots()anddeleteSnapshot(). - A dev server writes a single snapshot, again after each change: opening a writer on a committed snapshot replaces its entries on commit.
devtells drivers which snapshots dev servers wrote, andlistSnapshots()returns it asCollectionStorageSnapshot. - Adds the stored entry format: Astro serializes an entry into a
metadatastring and an optionalcontentstring (bodyandrendered), so drivers can skip content.
Testing
collection-storage-entries.test.tscovers the round trip and the metadata/content split.
Docs
- No docs yet, see the first PR of the stack.

Part of the implementation of the enhanced content collections RFC (collection storage).
Changes
- Adds the
experimental.collectionStorageDriversflag and astorageoption on build-time collections, which takes a storage descriptor ({ entrypoint, config }). - Loading the content config throws
CollectionStorageDriversNotEnabledwhen a collection setsstoragewithout the flag.
Testing
collection-storage-config.test.tscovers parsing and the flag check.define-collection-storage.tstype-checks thestorageoption.
Docs
- Not yet: the feature is not usable until the rest of the stack lands. Docs will come with the experimental flag page.

Changes
writeAssetImports()inmutable-data-store.tsno longer writes a second, differently-formatted empty map when the asset set is empty. Previously the empty-map branch wroteexport default new Map();and fell through, causing a second write with different whitespace. The watcher then saw.astro/content-assets.mjschange and sentfull-reload, which on the Cloudflare adapter cleared the module runner mid-request and produced React hook errors.- The fix adds
this.#assetsDirty = false; return;after the empty-branch write, matching the existing pattern inwriteModuleImports().
Testing
- Added a unit test in
packages/astro/test/units/content-collections/mutable-data-store.test.tscoveringstore.clear()when there are no asset imports, asserting thatwriteAssetImports()writes only once and that the result is the canonical empty-map string.
Docs
- No docs update needed; this is an internal dev-server correctness fix with no user-facing API change.
Closes #18573

Changes
<ClientRouter />now setshistory.scrollRestoration = 'auto'in apagehidelistener so a full reload lets the browser restore scroll position natively, before any JS runs. Previously the router kept'manual'forever, causing the page to paint at the top and then jump to the saved position after the module script executed.- A
pageshowlistener (bfcache restores) and the module init reset it back to'manual', so the router retains full control of scroll for its own client-side navigations.
Testing
- Added an e2e regression test in
packages/astro/e2e/view-transitions.test.ts("Reload leaves scroll restoration to the browser") that scrolls a page with<ClientRouter />, triggers a reload, and asserts thatscrollRestorationis'auto'at the point of unload, covering the newpagehidelistener.
Docs
- No docs update needed; this is an internal implementation fix with no API or configuration surface change.
Closes #18569
Last fetched: | Scheduled refresh: Every Saturday
See Customizing GitHub Activity Pages to configure your own
Inspired by prs.atinux.com



