This pull request's diff hasn't been prepared yet. Log in with GitHub to have us prepare it for review.

[ci] release #18459

Closed
astrobot-houston opened 7:05am on October 20, 2026 wanted to merge 1 commit into withastro/astro main from
changeset-release/main

Pull Request Overview

  • Opened on October 20, 2026
  • Status Closed
  • Commit count 1 with first commit October 21, 2026

Total Delta

0 Total Diff Delta

Open Days

Open 16 weekdays

Test Delta

0 Diff Delta in Test Files
Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Fraction of total time Business days Phase
 
0 days Authoring 0 commits before pull request opened for review
 
1 day Awaiting first review

Total time for pull request 1 business day from first commit to closed PR

Author avatar

[ci] release

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

[email protected]

Patch Changes


  • #18430 dda9ec3 Thanks @Abhirup-99! - Speeds up content sync with experimental.collectionStorage: "chunked" by computing each character's UTF-8 width from its code point instead of encoding every character through TextEncoder. On a store of ~44k entries this cuts the chunking step from about 60 seconds to well under a second, with byte-identical output.


  • #18438 5e0eaa4 Thanks @astro-factory! - Fixes astro dev with @astrojs/cloudflare failing with Calling `require` for "node-fetch" when a server dependency such as cross-fetch requires node-fetch


  • #18376 a4e201d Thanks @okxint! - Fixes astro dev treating a stale lock file containing a Linux thread ID as a running Astro server. A successful process lookup with no matching PID now marks the lock as stale, preventing astro dev stop and astro dev --force from killing the unrelated process that owns the thread.


  • #18467 d1fb7d3 Thanks @astro-factory! - Fixes the defineConfig() types for i18n.defaultLocale, i18n.fallback, and i18n.domains so they accept a custom locale's path instead of its codes, matching how Astro validates and uses these values


  • #18475 cf27e70 Thanks @ematipico! - Bumps the minimum supported Node.js version to 22.23.4, which includes the fixes from the October 2026 Node.js security releases


This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.


  • #18451 7a0ba6f Thanks @DenisCDev! - Fixes astro sync, astro check and astro build replacing the optimized dependencies of a dev server running in the same project, which broke framework islands in that dev server until it was restarted with --force


  • #18336 e943003 Thanks @astro-factory! - Fixes inline styles in dev so that framework-transformed CSS is used, such as scoped styles and v-bind() in Vue single-file components


  • #18399 829fc00 Thanks @astro-factory! - Fixes a dev server error (Could not find server component name) for a server:defer island that imports astro:actions or astro:config/server, when its page was not the first island page loaded after starting the server


  • #18330 4db9e0d Thanks @Samuteg! - Fixes the astro:env/server virtual module being generated with invalid JS in dev when any environment variable contains $ replacement patterns ($`, $&, $', $1, …). The inlined env JSON was passed as a string to String.replace, so e.g. the KITTY_PUBLIC_KEY value set by default in Kitty terminals corrupted the module and broke dev with Failed to parse source for import analysis



  • Updated dependencies [cf27e70]:



Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes


  • #18422 07700d4 Thanks @cyface! - Fixes the /_image endpoint returning a 500 error when href points to a missing file or a file that isn't an image. It now responds with a 404 or 400 instead.


  • #18465 f31f143 Thanks @astro-factory! - Fixes a custom src/fetch.ts rendering truncated pages without islands or hoisted scripts in astro dev when prerenderEnvironment: 'node' is set


  • #18461 8b77891 Thanks @astro-factory! - Fixes options passed to sharpImageService() being ignored when generating images at build time with imageService: 'compile'


  • #18468 119263a Thanks @astro-factory! - Fixes astro sync, astro check, and astro build overwriting the dependency cache of a running astro dev server, which caused it to fail with "The file does not exist ... in the optimize deps directory" errors



  • Updated dependencies []:



Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.
- Updated dependencies [cf27e70]:
- @astrojs/[email protected]

@astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.
- Updated dependencies []:
- @astrojs/[email protected]

@astrojs/[email protected]

Patch Changes



  • #18439 3e80f04 Thanks @hanford! - Updates Partytown to 1.0.1, which preserves queued events when falling back to the main thread with dataLayer.push forwarded using preserveBehavior.
    ## @astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes



  • #18455 7af66fc Thanks @astro-factory! - Fixes the astro-check binary ignoring its first two command-line arguments, so flags such as --help, --root, --watch, and --tsconfig are respected again. If your scripts padded the arguments to work around this (for example, astro-check -- -- --tsconfig ./tsconfig.app.json), remove the padding.

  • Updated dependencies [044148d]:



Patch Changes

Patch Changes

Patch Changes

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.

@astrojs/[email protected]

Patch Changes

This is a patch release because the Node.js support and upgrade policy allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.



  • #18466 d7f5c54 Thanks @astro-factory! - Fixes @astrojs/upgrade [version] ignoring an exact version number (for example npx @astrojs/upgrade 7.3.8) and upgrading to the latest release instead

Comments Threads Pending Resolution

Resolved Comment Threads

No resolved comments have been left on this PR.