[ci] release

[astrobot-houston]

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/[email protected]

Minor Changes

• #12768 524c855 Thanks @ematipico! - Adds a new buildOutput property to the API createRedirectsFromAstroRoutes

[email protected]

Patch Changes

• #12798 7b0cb85 Thanks @ascorbic! - Improves warning logs for invalid content collection configuration

• #12781 96c4b92 Thanks @ascorbic! - Fixes a regression that caused default() to not work with reference()

• #12820 892dd9f Thanks @ascorbic! - Fixes a bug that caused cookies to not be deleted when destroying a session

• #12864 440d8a5 Thanks @kaytwo! - Fixes a bug where the session ID wasn't correctly regenerated

• #12768 524c855 Thanks @ematipico! - Fixes an issue where Astro didn't print error logs when Astro Islands were used in incorrect cases.

• #12814 f12f111 Thanks @ematipico! - Fixes an issue where Astro didn't log anything in case a file isn't created during the build.

• #12875 e109002 Thanks @ascorbic! - Fixes a bug in emulated legacy collections where the entry passed to the getCollection filter function did not include the legacy entry fields.

• #12768 524c855 Thanks @ematipico! - Fixes an issue where Astro was printing the incorrect output format when running the astro build command

• #12810 70a9f0b Thanks @louisescher! - Fixes server islands failing to check content-type header under certain circumstances

  Sometimes a reverse proxy or similar service might modify the content-type header to include the charset or other parameters in the media type of the response. This previously wasn't handled by the client-side server island script and thus removed the script without actually placing the requested content in the DOM. This fix makes it so the script checks if the header starts with the proper content type instead of exactly matching text/html, so the following will still be considered a valid header: text/html; charset=utf-8

• #12816 7fb2184 Thanks @ematipico! - Fixes an issue where an injected route entrypoint wasn't correctly marked because the resolved file path contained a query parameter.

  This fixes some edge case where some injected entrypoint were not resolved when using an adapter.

@astrojs/[email protected]

Patch Changes

• #12829 ebe2aa9 Thanks @SapphicMoe! - Revert incorrect Content-Type header applied for RSS XML file

@astrojs/[email protected]

Patch Changes

• #12822 1fab2f2 Thanks @stdavis! - Updates the partytown dependency to the new npm org name and latest version.

@astrojs/[email protected]

Patch Changes

• #12776 8809b85 Thanks @aminevg! - Fixes an issue where TypeScript couldn't infer the correct types of the server.mjs file

@astrojs/[email protected]

Patch Changes

• #12776 8809b85 Thanks @aminevg! - Fixes an issue where TypeScript couldn't infer the correct types of the server.mjs file