fix(deps): update astro

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/starlight (source)	^0.34.4 -> ^0.35.1
astro (source)	^5.10.1 -> ^5.12.1

---

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.35.1

Compare Source

Patch Changes

• #​3325 4cf28f2 Thanks @​mniinio! - Adds Finnish language support

v0.35.0

Compare Source

Minor Changes

• #​2261 778b743 Thanks @​shubham-padia! - Adds support for using any of Starlight’s built-in icons in asides.

• #​3272 e7fe267 Thanks @​delucis! - Adds a new generateId option to Starlight’s docsLoader()

  This enables overriding the default sluggifier used to convert content filenames to URLs.

• #​3276 3917b20 Thanks @​delucis! - Excludes banner content from search results

  Previously, content set in banner in page frontmatter was indexed by Starlight’s default search provider Pagefind. This could cause unexpected search results, especially for sites setting a common banner content on multiple pages. Starlight’s default Banner component is now excluded from search indexing.

  This change does not impact Banner overrides using custom components.

• #​3266 1161af0 Thanks @​HiDeoo! - Adds support for custom HTML attributes on autogenerated sidebar links using the autogenerate.attrs option.

• #​3274 80ccff7 Thanks @​HiDeoo! - Fixes an issue where some Starlight remark and rehype plugins were transforming Markdown and MDX content in non-Starlight pages.

  ⚠️ BREAKING CHANGE:

  Previously, some of Starlight’s remark and rehype plugins, most notably the plugin transforming Starlight's custom Markdown syntax for rendering asides, were applied to all Markdown and MDX content. This included content from individual Markdown pages and content from content collections other than the docs collection used by Starlight.

  This change restricts the application of Starlight’s remark and rehype plugins to only Markdown and MDX content loaded using Starlight's docsLoader(). If you were relying on this behavior, please let us know about your use case in the dedicated #starlight channel in the Astro Discord or by opening an issue.

Patch Changes

• #​3266 1161af0 Thanks @​HiDeoo! - Ensures invalid sidebar group configurations using the attrs option are properly reported as a type error.

  Previously, invalid sidebar group configurations using the attrs option were not reported as a type error but only surfaced at runtime. This change is only a type-level change and does not affect the runtime behavior of Starlight which does not support the attrs option for sidebar groups.

• #​3274 80ccff7 Thanks @​HiDeoo! - Prevents Starlight remark and rehype plugins from transforming Markdown and MDX content when using the Astro renderMarkdown() content loader API.

v0.34.8

Compare Source

Patch Changes

• #​3306 21fcd94 Thanks @​HiDeoo! - Fixes a regression in Starlight version 0.34.5 that caused multilingual sites with a default locale explicitly set to root to report a configuration error.

v0.34.7

Compare Source

Patch Changes

• #​3298 7bd02e3 Thanks @​HiDeoo! - Fixes a potential issue with absolutePathToLang() plugin API not handling paths with spaces correctly.

v0.34.6

Compare Source

Patch Changes

• #​3293 88f0d34 Thanks @​HiDeoo! - Fixes an issue preventing to override the slug of a page with the slug frontmatter property using the / value.

v0.34.5

Compare Source

Patch Changes

• #​3282 7680e87 Thanks @​alvinometric! - Moves padding of <main> element to a --sl-main-pad CSS custom property to simplify setting custom values

• #​3288 131371e Thanks @​HiDeoo! - Fixes a potential configuration issue for multilingual sites with a default language including a regional subtag.

withastro/astro (astro)

v5.12.1

Compare Source

Patch Changes

• #​14094 22e9087 Thanks @​ascorbic! - Correct types to allow priority on all images

• #​14091 26c6b6d Thanks @​ascorbic! - Fixes a bug that caused a type error when defining session options without a driver

• #​14082 93322cb Thanks @​louisescher! - Fixes an issue where Astro's default 404 route would incorrectly match routes containing "/404" in dev

• #​14089 687d253 Thanks @​florian-lefebvre! - Fixes a case where astro:env would not load the right environments variables in dev

• #​14092 6692c71 Thanks @​ascorbic! - Improves error handling in live collections

• #​14074 144a950 Thanks @​abcfy2! - Fixes a bug that caused some image service builds to fail

• #​14092 6692c71 Thanks @​ascorbic! - Fixes a case where zod could not be imported from astro:content virtual module in live collection config

v5.12.0

Compare Source

Minor Changes

• #​13971 fe35ee2 Thanks @​adamhl8! - Adds an experimental flag rawEnvValues to disable coercion of import.meta.env values (e.g. converting strings to other data types) that are populated from process.env

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type.

  However, Astro also converts your environment variables used through import.meta.env in some cases, and this can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.rawEnvValues flag disables coercion of import.meta.env values that are populated from process.env, allowing you to use the raw value.

  To enable this feature, add the experimental flag in your Astro config:

  import { defineConfig } from "astro/config"
  
  export default defineConfig({
  +  experimental: {
  +    rawEnvValues: true,
  +  }
  })

  If you were relying on this coercion, you may need to update your project code to apply it manually:

  - const enabled: boolean = import.meta.env.ENABLED
  + const enabled: boolean = import.meta.env.ENABLED === "true"

  See the experimental raw environment variables reference docs for more information.

• #​13941 6bd5f75 Thanks @​aditsachde! - Adds support for TOML files to Astro's built-in glob() and file() content loaders.

  In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader.

  Astro 5.12 now directly supports loading data from TOML files in content collections in both the glob() and the file() loaders.

  If you had added your own TOML content parser for the file() loader, you can now remove it as this functionality is now included:

  // src/content.config.ts
  import { defineCollection } from "astro:content";
  import { file } from "astro/loaders";
  - import { parse as parseToml } from "toml";
  const dogs = defineCollection({
  -  loader: file("src/data/dogs.toml", { parser: (text) => parseToml(text) }),
  + loader: file("src/data/dogs.toml")
    schema: /* ... */
  })

  Note that TOML does not support top-level arrays. Instead, the file() loader considers each top-level table to be an independent entry. The table header is populated in the id field of the entry object.

  See Astro's content collections guide for more information on using the built-in content loaders.

Patch Changes

• Updated dependencies [6bd5f75]:
  • @​astrojs/markdown-remark@​6.3.3

v5.11.2

Compare Source

Patch Changes

• #​14064 2eb77d8 Thanks @​jp-knj! - Allows using tsconfig compilerOptions.paths without setting compilerOptions.baseUrl

• #​14068 10189c0 Thanks @​jsparkdev! - Fixes the incorrect CSS import path shown in the terminal message during Tailwind integration setup.

v5.11.1

Compare Source

Patch Changes

• #​14045 3276b79 Thanks @​ghubo! - Fixes a problem where importing animated .avif files returns a NoImageMetadata error.

• #​14041 0c4d5f8 Thanks @​dixslyf! - Fixes a <ClientRouter /> bug where the fallback view transition animations when exiting a page
  ran too early for browsers that do not support the View Transition API.
  This bug prevented event.viewTransition?.skipTransition() from skipping the page exit animation
  when used in an astro:before-swap event hook.

v5.11.0

Compare Source

Minor Changes

• #​13972 db8f8be Thanks @​ematipico! - Updates the NodeApp.match() function in the Adapter API to accept a second, optional parameter to allow adapter authors to add headers to static, prerendered pages.

  NodeApp.match(request) currently checks whether there is a route that matches the given Request. If there is a prerendered route, the function returns undefined, because static routes are already rendered and their headers cannot be updated.

  When the new, optional boolean parameter is passed (e.g. NodeApp.match(request, true)), Astro will return the first matched route, even when it's a prerendered route. This allows your adapter to now access static routes and provides the opportunity to set headers for these pages, for example, to implement a Content Security Policy (CSP).

Patch Changes

• #​14029 42562f9 Thanks @​ematipico! - Fixes a bug where server islands wouldn't be correctly rendered when they are rendered inside fragments.

  Now the following examples work as expected:

v5.10.2

Compare Source

Patch Changes

• #​14000 3cbedae Thanks @​feelixe! - Fix routePattern JSDoc examples to show correct return values

• #​13990 de6cfd6 Thanks @​isVivek99! - Fixes a case where astro:config/client and astro:config/server virtual modules would not contain config passed to integrations updateConfig() during the build

• #​14019 a160d1e Thanks @​ascorbic! - Removes the requirement to set type: 'live' when defining experimental live content collections

  Previously, live collections required a type and loader configured. Now, Astro can determine that your collection is a live collection without defining it explicitly.

  This means it is now safe to remove type: 'live' from your collections defined in src/live.config.ts:

  import { defineLiveCollection } from 'astro:content';
  import { storeLoader } from '@​mystore/astro-loader';
  
  const products = defineLiveCollection({
  -  type: 'live',
    loader: storeLoader({
      apiKey: process.env.STORE_API_KEY,
      endpoint: 'https://api.mystore.com/v1',
    }),
  });
  
  export const collections = { products };

  This is not a breaking change: your existing live collections will continue to work even if you still include type: 'live'. However, we suggest removing this line at your earliest convenience for future compatibility when the feature becomes stable and this config option may be removed entirely.

• #​13966 598da21 Thanks @​msamoylov! - Fixes a broken link on the default 404 page in development

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[netlify]

✅ Deploy Preview for openpodcastapi ready!

Name	Link
🔨 Latest commit	d3f1c2b
🔍 Latest deploy log	https://app.netlify.com/projects/openpodcastapi/deploys/687e6be28699890007bc8264
😎 Deploy Preview	https://deploy-preview-131--openpodcastapi.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.