AstroEco is Contributing…

This PR ensures proper params are being parsed and sent to the libsql Client, due to URLSearchParams being a Record<string, string> this object requires parsing to ensure the values are being parsed to number or boolean.

See https://discord.com/channels/830184174198718474/1370190284855705680 for context.

Testing

Added a new unit test for ensuring the URL parsing is correct in various circumstances.

Docs

This PR corrects internal logic to reflect the information on the docs. No docs changes needed.

[ci] release

withastro/astro

#13771 May 8

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/sitemap@3.4.0

Minor Changes

#13753 90293de Thanks @mattyoho! - Customize the filenames of sitemap XML files generated by the @astro/sitemap integration by setting filenameBase in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.

Generated sitemap files will appear at /sitemap-0.xml and /sitemap-index.xml by default, which may conflict with preexisting files. Set filenameBase to a custom value to avoid that if so:
```
import { defineConfig } from 'astro/config';
import sitemap from '@astrojs/sitemap';

export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      filenameBase: 'astronomy-sitemap',
    }),
  ],
});
```
This will yield sitemap and index files as https://example.com/astronomy-sitemap-0.xml and https://example.com/astronomy-sitemap-index.xml.

Cookie API website for Showcase

withastro/starlight

#3188 May 8

Description

Closes #
What does this PR change? Give us a brief description.
Did you change something visual? A before/after screenshot can be helpful.

Expand `ActionError` codes to include all IANA HTTP error codes

withastro/astro

#13769 May 8

Changes

Expand ActionError codes to include all IANA-registered HTTP error codes. Related discussion.

Possible issues that can affect existing projects:

405 TIMEOUT replaced by 405 METHOD_NOT_ALLOWED, which is the accurate name for the 405 code. REQUEST_TIMEOUT is 408.
413 PAYLOAD_TOO_LARGE replaced by 413 CONTENT_TOO_LARGE.
499 CLIENT_CLOSED_REQUEST removed as non-standard.

Testing

No tests written. Tested by linking the local astro fork using pnpm link.

Docs

The expanded list of error codes doesn’t affect existing documented behavior.

feat: add cache hint support to live loaders

withastro/astro

#13767 May 8

Changes

Adds support for returning a cacheHint object with entries and collections. This can be used to suggest cache tags or ttl for the data, and in future could be integrated with route caching

Testing

Docs

Added new error for invalid cache hints

fix(fonts): relative protocol urls

withastro/astro

#13765 May 8

Changes

Closes #13754
Some remote font providers return protocol relative URLs (starting with //), which are then considered absolute by the font fetcher and fails
Now when we normalize remote font data, we default this kind of URL to https

Testing

Unit + manual

Docs

Changeset

feat: add schema parsing to live collections

withastro/astro

#13763 May 7

Changes

Adds schema parsing to live content collections.

parses the returned data from getCollection and getEntry
updates types so that if schema is defined, collections will be typed using that rather than the loader type
refactors error handling and adds more checks for the config and the data

Testing

Still needs tests

Docs

Added a new error

add showcase sonar

withastro/starlight

#3183 May 7

This pull request introduces a new showcase to highlight specific features or use cases of starlight. It aims to improve visibility and demonstrate practical applications for users or contributors.

Let me know if any adjustments are needed!

refactor(astro): put them to follow a pattern for errors

withastro/astro

#13761 May 6

Changes

#13759 (comment)
Introduced two scoped error definitions in packages/astro/src/core/errors/errors-data.ts
- FileGlobNotSupported – thrown when a glob pattern is passed to file() loader.
- FileParserNotFound – thrown when no parser can be determined for the file extension.
  Both follow the project’s error‐data convention (name | title | message | hint | docs tags).
Replaced generic Error throws with AstroError in
packages/astro/src/content/loader/file.ts.
- throw new AstroError(FileGlobNotSupported)
- throw new AstroError({ …FileParserNotFound, message: FileParserNotFound.message(fileName) })
Added a changeset (pnpm exec changeset) so these improvements surface in release notes.

Testing

Ran the full test suite: pnpm test – no regressions.
Manual Smoke Tests
1. file('data/*.json') → displays File glob pattern not supported banner.
2. file('data/example.xml') → displays File parser not found banner with doc link.

No new automated tests — behaviour is unchanged; only error wiring differs.

Docs

No public-API changes. Docs remain valid.

[ci] release

withastro/astro

#13760 May 6

Releases

astro@5.7.12

Patch Changes

#13752 a079c21 Thanks @florian-lefebvre! - Improves handling of font URLs not ending with a file extension when using the experimental fonts API
#13750 7d3127d Thanks @martrapp! - Allows the ClientRouter to open new tabs or windows when submitting forms by clicking while holding the Cmd, Ctrl, or Shift key.
#13765 d874fe0 Thanks @florian-lefebvre! - Fixes a case where font sources with relative protocol URLs would fail when using the experimental fonts API
#13640 5e582e7 Thanks @florian-lefebvre! - Allows inferring weight and style when using the local provider of the experimental fonts API

If you want Astro to infer those properties directly from your local font files, leave them undefined:
```
{
  // No weight specified: infer
  style: 'normal'; // Do not infer
}
```

Prevent heading anchor links on non-Starlight content

withastro/starlight

#3181 May 6

Description

Closes #3175

In Starlight 0.34.0, support for generating clickable anchor links for headings was added. For Markdown and MDX content, a rehype plugin is used to generate the links.

When the feature is not disabled, this plugin runs unconditionally, which means that these links are generated for non-Starlight content like individual Markdown page or content not from the Starlight docs content collection.

This PR prevents this behavior by checking if the virtual file path is part of the Starlight docs content collection first, and bails if it is not.

For testing, I relied on E2E tests as it seems that on Windows, file path separators are inconsistent when the rehype plugin is used on Markdown vs MDX files. I'll investigate and open a separate issue/PR for that on the Astro repo.

Here is a preview of the changes before and after the fix for an individual Markdown page:

Before	After

refactor(astro): Replaced generic `Error` throws with `AstroError`

withastro/astro

#13759 May 6

Changes

remove todo comments
Replaced generic Error throws with AstroError in packages/astro/src/content/loader/file.ts.
- Adds contextual error names and messages:
  - Glob Pattern Error for disallowing * in file() loader paths.
  - Parser Not Found when no parser is available for the file extension.
- Imports AstroError from core/errors so all runtime errors funnel through our unified error-handling layer.
Changeset included (pnpm exec changeset) to surface in release notes.

Testing

Ran the full test suite: pnpm test – all existing tests pass.
Manual sanity check:
1. Created a sample project with a bad data/*.json glob; verified the new Glob Pattern Error message surfaces in the terminal with the Astro error banner.
2. Pointed the loader to an .xml file; saw the Parser Not Found message and helpful suggestion.

No additional tests added because logic remains identical; only the error-reporting wrapper changed.

Docs

No user-facing API changes. Docs remain valid.

feat(fonts): warn when no data

withastro/astro

#13756 May 6

Changes

As a user, it can be challenging to understand why fonts may not be working
To help with that, we now log a warning when a remote provider returns no data for a given family

Testing

Units

Docs

Changeset

refactor(example): remove todo comment and normalize network errors

withastro/astro

#13755 May 6

Changes

remove todo comment
Renamed helper
get<T> → getJson<T> to clarify that the helper always returns parsed JSON.
Timeout & abort support
Adds an AbortController with a 10 s default timeout to prevent hanging requests.
Richer error messages
- Distinguishes HTTP errors (GET /api … → 503) from network/abort errors (failed: The user aborted a request).
- Includes status text for quicker debugging.
Less boilerplate
Helper now returns response.json() directly, so the four public API functions no longer need their own inline callbacks.
No functional change to callers
Signatures of getProducts(), getProduct(), getUser(), and getCart() remain identical; only internal implementation is updated.
Changeset included
pnpm exec changeset this is purely internal refactor. not add.

Testing

Unit: pnpm test — all existing tests pass.
Manual:
1. Started dev server, loaded /products page – data still renders.
2. Throttled network in DevTools → request now aborts at 10 s with descriptive console error.
3. Verified addToUserCart() still posts successfully.

No new automated tests added because the helper is already covered by higher-level API tests; timeout behaviour is best validated manually.

Docs

No public-facing API surface changed, so docs update not required.

/cc @withastro/maintainers-docs for visibility, but I believe no docs edits are needed.

Add a config option for filenames generated by the @astrojs/sitemap integration

withastro/astro

#13753 May 5

Changes

This adds a configuration option for the @astrojs/sitemap integration for setting the base filename for the generated sitemap XML files.

Impact on existing users

The new configuration setting is defaulted to a value that matches current behavior so that existing users won't be impacted.

Use case

Scenario: Astro is chosen for adding informational content pages for an existing product website at a set of top-level content categories, e.g., Docs, Blog, and Changelog. The content verticals need to be hosted on the root domain at /docs, /blog, and /changelog, respectively.

E.g., the Docs URL will be https://example.com/docs.

Problem: Currently, the generated sitemap files want to live at https://example.com/sitemap-index.xml and https://example.com/sitemap-{n}.xml, which will potentially conflict with an existing sitemap.xml for the root domain.

Solution: Add a config setting to change the generated filename so that the files can be integrated into a pre-existing sitemap-index.xml via other external tooling.

// https://astro.build/config
export default defineConfig({
  site: "https://example.com",
  integrations: [
    sitemap({
      filenameBase: "content-sitemap",
    }),
  ],
});

Testing

A test was added to the relevant test file. The change was also tested in a live Astro app using a local build of the integration package.

Docs

Documentation for the setting could / should be added to the related guide. Initial suggested changes PR has been opened here: withastro/docs#11614.

/cc @withastro/maintainers-docs for feedback!

fix(fonts): handle urls without extensions

withastro/astro

#13752 May 5

Changes

Closes #13743
Until this PR, we assumed the font files urls returned by providers would end with a file extension eg. .woff2
However this is not always the case (eg. adobe)
To fix this, I moved the type extraction so that remote providers and local providers handle it differently
- local provider: keep the previous behavior ie. extract the type from the url
- remote provider: try use source.format (given by unifont) then fallback to extracting the type from the url

Testing

Tests updated and added. Affected user confirmed it works using the preview release

Docs

Changeset

feat(fonts): update unifont

withastro/astro

#13751 May 5

Changes

Support google subsetting

Testing

N/A

Docs

Changeset

ClientRouter: honor ctrl/shift... keys when clicking submit

withastro/astro

#13750 May 5

Changes

When submitting a form, the client router now delegates back to the browser when the user holds hift alt or cmd/ctrl keys while clicking submit. This allows the browser to open a new tab / window or download. These are all cases where you won't get view transitions anyhow.

Closes #13744

Testing

tested manually

Docs

n.a., bug fix

fix(deps): update astro dependencies

withastro/astro

#13749 May 5

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/compiler (source)	`^2.11.0` -> `^2.12.0`
@playwright/test (source)	`^1.51.1` -> `^1.52.0`
@preact/signals (source)	`2.0.2` -> `2.0.4`
@tailwindcss/vite (source)	`^4.0.17` -> `^4.1.6`
@types/react (source)	`^18.3.20` -> `^18.3.21`
@types/react-dom (source)	`^18.3.5` -> `^18.3.7`
es-module-lexer	`^1.6.0` -> `^1.7.0`
expect-type	`^1.2.0` -> `^1.2.1`
http-cache-semantics	`^4.1.1` -> `^4.2.0`
linkedom	`^0.18.9` -> `^0.18.10`
lit (source)	`^3.2.1` -> `^3.3.0`
node-mocks-http	`^1.16.2` -> `^1.17.2`
package-manager-detector	`^1.1.0` -> `^1.3.0`
postcss-preset-env (source)	`^10.1.5` -> `^10.1.6`
preact (source)	`^10.26.4` -> `^10.26.6`
react (source)	`19.0.0` -> `19.1.0`
react-dom (source)	`19.0.0` -> `19.1.0`
remark-rehype	`^11.1.1` -> `^11.1.2`
rollup (source)	`^4.37.0` -> `^4.40.2`
sass	`^1.86.0` -> `^1.87.0`
shiki (source)	`^3.2.1` -> `^3.4.0`
solid-js (source)	`^1.9.5` -> `^1.9.6`
svelte (source)	`^5.25.3` -> `^5.28.2`
tailwindcss (source)	`^4.0.17` -> `^4.1.6`
tinyglobby	`^0.2.12` -> `^0.2.13`
typescript (source)	`^5.8.2` -> `^5.8.3`
undici (source)	`^7.5.0` -> `^7.8.0`
unstorage (source)	`^1.15.0` -> `^1.16.0`
vite (source)	`^6.3.4` -> `^6.3.5`
vitest (source)	`^3.0.9` -> `^3.1.3`
yocto-spinner	`^0.2.1` -> `^0.2.2`
zod (source)	`^3.24.2` -> `^3.24.4`