Build(deps): Bump the patch-updates group with 2 updates

[dependabot]

Bumps the patch-updates group with 2 updates: astro and svelte.

Updates astro from 5.16.7 to 5.16.9

Release notes

Sourced from astro's releases.

astro@5.16.9

Patch Changes

• #15174 37ab65a 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';
  export default defineConfig({
  experimental: {
  fonts: [
  {
  name: 'Material Symbols Outlined',
  provider: fontProviders.googleicons(),
  cssVariable: '--font-material',
  },
  ],
  },
  });

• #15150 a77c4f4 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.

• #15130 9b726c4 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

• #15174 37ab65a 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';
  export default defineConfig({
  experimental: {
  fonts: [
  {
  name: 'Material Symbols Outlined',
  provider: fontProviders.googleicons(),
  cssVariable: '--font-material',
  },
  ],
  },
  });

• #15150 a77c4f4 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.

• #15130 9b726c4 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

Updates svelte from 5.46.1 to 5.46.3

Release notes

Sourced from svelte's releases.

svelte@5.46.3

Patch Changes

• fix: reconnect clean deriveds when they are read in a reactive context (#17362)

Changelog

Sourced from svelte's changelog.

5.46.3

Patch Changes

• fix: reconnect clean deriveds when they are read in a reactive context (#17362)

5.46.2

Patch Changes

• fix: don't transform references of function declarations in legacy mode (#17431)

• fix: notify deriveds of changes to sources inside forks (#17437)

• fix: always reconnect deriveds in get, when appropriate (#17451)

• fix: prevent derives without dependencies from ever re-running (286b40c4526ce9970cb81ddd5e65b93b722fe468)

• fix: correctly update writable deriveds inside forks (#17437)

• fix: remove $inspect calls after await expressions when compiling for production server code (#17407)

• fix: clear batch between runs (#17424)

• fix: adjust loc property of Program nodes created from <script> elements (#17428)

• fix: don't revert source to UNINITIALIZED state when time travelling (#17409)

Commits

• ed8dcd0 Version Packages (#17458)
• 51c7f71 Version Packages (#17410)
• 7dbb5b4 fix: derived reactivity and perf regressions (#17362)
• ae224be fix: always reconnect deriveds in get, when appropriate (#17451)
• 2c23390 chore: const -> var
• 286b40c fix: prevent derives without dependencies from ever re-running (#17445)
• f8bdadc chore: simplify is_dirty (#17444)
• 359be81 chore: tidy up (#17443)
• f04f22e chore: use update_derived_status instead of set_signal_status where appropria...
• c6ce1ff chore: move set_signal_status into separate module (#17441)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
blog	Ready	Preview, Comment	Jan 13, 2026 3:18am

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	rc-blog	0f51de6	Commit Preview URL Branch Preview URL	Jan 13 2026, 03:19 AM