Bump astro from 5.13.10 to 5.16.9

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Bumps astro from 5.13.10 to 5.16.9.

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {
  const provider = acmeProvider(config);

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.9

Patch Changes

• #1517437ab65a Thanks @​florian-lefebvre! - Adds Google Icons to built-in font providers

  To start using it, access it on fontProviders:

  import{defineConfig,fontProviders}from'astro/config';exportdefaultdefineConfig({experimental: {fonts: [{name: 'Material Symbols Outlined',provider: fontProviders.googleicons(),cssVariable: '--font-material',},],},});

• #15150a77c4f4 Thanks @​matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

  Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

• #151309b726c4 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Changes how font providers are implemented with updates to the FontProvider type

  This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

  Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

  Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

  What should I do?

  If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
  +import type { FontProvider } from "astro";+import type { InitializedProvider } from 'unifont';+function acme(config?: AcmeOptions): FontProvider {

... (truncated)

Commits

• 7f449b7 [ci] release (#15159)
• 37ab65a feat(fonts): export googleicons provider (#15174)
• 4636348 [ci] format
• 9b726c4 feat(fonts)!: update font provider API (#15130)
• 337bca1 [ci] format
• a77c4f4 Fix hydration for framework components in MDX slots (#15150)
• 9cd5b87 fix: scripts not rendering with unused Fragment slots (#13847) (#15147)
• f88b852 [ci] release (#15132)
• 39ee41f fix: Accept setCookie from both context and headers (#15152)
• 34f84c2 fix(toolbar): skip image audit for framework components (#15149)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.