fix(deps): update astro

[github-actions]

This PR contains the following updates:

Package	Type	Update	Change
astro (source)	dependencies	patch	5.16.11 -> 5.16.15
astro-navbar	dependencies	minor	2.3.7 -> 2.4.0

---

Release Notes

withastro/astro (astro)

v5.16.15

Compare Source

Patch Changes

• #​15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

v5.16.14

Compare Source

Patch Changes

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

  Updates how the local provider must be used when using the experimental Fonts API

  Previously, there were 2 kinds of font providers: remote and local.

  Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

  -import { defineConfig } from "astro/config";
  +import { defineConfig, fontProviders } from "astro/config";
  
  export default defineConfig({
      experimental: {
          fonts: [{
              name: "Custom",
              cssVariable: "--font-custom",
  -            provider: "local",
  +            provider: fontProviders.local(),
  +            options: {
              variants: [
                  {
                      weight: 400,
                      style: "normal",
                      src: ["./src/assets/fonts/custom-400.woff2"]
                  },
                  {
                      weight: 700,
                      style: "normal",
                      src: ["./src/assets/fonts/custom-700.woff2"]
                  }
                  // ...
              ]
  +            }
          }]
      }
  });

  Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

  See the experimental Fonts API docs for more information.

• #​15213 c775fce Thanks @​florian-lefebvre! - Exposes root on FontProvider init() context

  When building a custom FontProvider for the experimental Fonts API, the init() method receives a context. This context now exposes a root URL, useful for resolving local files:

  import type { FontProvider } from "astro";
  
  export function registryFontProvider(): FontProvider {
    return {
      // ...
  -    init: async ({ storage }) => {
  +    init: async ({ storage, root }) => {
          // ...
      },
    };
  }

• #​15185 edabeaa Thanks @​EricGrill! - Add .vercel to .gitignore when adding the Vercel adapter via astro add vercel

v5.16.13

Compare Source

Patch Changes

• #​15182 cb60ee1 Thanks @​florian-lefebvre! - Adds a new getFontBuffer() method to retrieve font file buffers when using the experimental Fonts API

  The getFontData() helper function from astro:assets was introduced in 5.14.0 to provide access to font family data for use outside of Astro. One of the goals of this API was to be able to retrieve buffers using URLs.

  However, it turned out to be impactical and even impossible during prerendering.

  Astro now exports a new getFontBuffer() helper function from astro:assets to retrieve font file buffers from URL returned by getFontData(). For example, when using satori to generate OpenGraph images:

  // src/pages/og.png.ts
  
  import type{ APIRoute } from "astro"
  -import { getFontData } from "astro:assets"
  +import { getFontData, getFontBuffer } from "astro:assets"
  import satori from "satori"
  
  export const GET: APIRoute = (context) => {
    const data = getFontData("--font-roboto")
  
    const svg = await satori(
      <div style={{ color: "black" }}>hello, world</div>,
      {
        width: 600,
        height: 400,
        fonts: [
          {
            name: "Roboto",
  -          data: await fetch(new URL(data[0].src[0].url, context.url.origin)).then(res => res.arrayBuffer()),
  +          data: await getFontBuffer(data[0].src[0].url),
            weight: 400,
            style: "normal",
          },
        ],
      },
    )
  
    // ...
  }

  See the experimental Fonts API documentation for more information.

v5.16.12

Compare Source

Patch Changes

• #​15175 47ae148 Thanks @​florian-lefebvre! - Allows experimental Font providers to specify family options

  Previously, an Astro FontProvider could only accept options at the provider level when called. That could result in weird data structures for family-specific options.

  Astro FontProviders can now declare family-specific options, by specifying a generic:

  // font-provider.ts
  import type { FontProvider } from "astro";
  import { retrieveFonts, type Fonts } from "./utils.js",
  
  interface Config {
    token: string;
  }
  
  +interface FamilyOptions {
  +    minimal?: boolean;
  +}
  
  -export function registryFontProvider(config: Config): FontProvider {
  +export function registryFontProvider(config: Config): FontProvider<FamilyOptions> {
    let data: Fonts = {}
  
    return {
      name: "registry",
      config,
      init: async () => {
        data = await retrieveFonts(token);
      },
      listFonts: () => {
        return Object.keys(data);
      },
  -    resolveFont: ({ familyName, ...rest }) => {
  +    // options is typed as FamilyOptions
  +    resolveFont: ({ familyName, options, ...rest }) => {
        const fonts = data[familyName];
        if (fonts) {
          return { fonts };
        }
        return undefined;
      },
    };
  }

  Once the font provider is registered in the Astro config, types are automatically inferred:

  // astro.config.ts
  import { defineConfig } from "astro/config";
  import { registryFontProvider } from "./font-provider";
  
  export default defineConfig({
      experimental: {
          fonts: [{
              provider: registryFontProvider({
                token: "..."
              }),
              name: "Custom",
              cssVariable: "--font-custom",
  +            options: {
  +                minimal: true
  +            }
          }]
      }
  });

• #​15175 47ae148 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Updates how options are passed to the Google and Google Icons font providers when using the experimental Fonts API

  Previously, the Google and Google Icons font providers accepted options that were specific to given font families.

  These options must now be set using the options property instead. For example using the Google provider:

  import { defineConfig, fontProviders } from "astro/config";
  
  export default defineConfig({
      experimental: {
          fonts: [{
              name: 'Inter',
              cssVariable: '--astro-font-inter',
              weights: ['300 900'],
  -            provider: fontProviders.google({
  -                experimental: {
  -                    variableAxis: {
  -                        Inter: { opsz: ['14..32'] }
  -                    }
  -                }
  -            }),
  +            provider: fontProviders.google(),
  +            options: {
  +                experimental: {
  +                    variableAxis: { opsz: ['14..32'] }
  +                }
  +            }
          }]
      }
  })

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

  Removes getFontData() exported from astro:assets with fontData when using the experimental Fonts API

  Accessing font data can be useful for advanced use cases, such as generating meta tags or Open Graph images. Before, we exposed a getFontData() helper function to retrieve the font data for a given cssVariable. That was however limiting for programmatic usages that need to access all font data.

  The getFontData() helper function is removed and replaced by a new fontData object:

  -import { getFontData } from "astro:assets";
  -const data = getFontData("--font-roboto")
  
  +import { fontData } from "astro:assets";
  +const data = fontData["--font-roboto"]

  We may reintroduce getFontData() later on for a more friendly DX, based on your feedback.

• #​15254 8d84b30 Thanks @​lamalex! - Fixes CSS assetsPrefix with remote URLs incorrectly prepending a forward slash

  When using build.assetsPrefix with a remote URL (e.g., https://cdn.example.com) for CSS assets, the generated <link> elements were incorrectly getting a / prepended to the full URL, resulting in invalid URLs like /https://cdn.example.com/assets/style.css.

  This fix checks if the stylesheet link is a remote URL before prepending the forward slash.

• #​15178 731f52d Thanks @​kedarvartak! - Fixes an issue where stopping the dev server with q+enter incorrectly created a dist folder and copied font files when using the experimental Fonts API

• #​15230 3da6272 Thanks @​rahuld109! - Fixes greedy regex in error message markdown rendering that caused link syntax examples to capture extra characters

• #​15253 2a6315a Thanks @​matthewp! - Fixes hydration for React components nested inside HTML elements in MDX files

• #​15227 9a609f4 Thanks @​matthewp! - Fixes styles not being included for conditionally rendered Svelte 5 components in production builds

• #​14607 ee52160 Thanks @​simensfo! - Reintroduces css deduplication for hydrated client components. Ensures assets already added to a client chunk are not flagged as orphaned

surjithctly/astro-navbar (astro-navbar)

v2.4.0

Compare Source

• Changed minimum scrollY to 50.

Full Changelog: surjithctly/astro-navbar@v2.3.9...v2.4.0

v2.3.9

Compare Source

Fixed: Add is:inline to script.

Full Changelog: surjithctly/astro-navbar@v2.3.8...v2.3.9

v2.3.8

Compare Source

Fixed: Navbar doesn't keep style on scroll after View transitions: See: https://github.com/surjithctly/astro-navbar/issues/29

Thanks @​KemaneWright and @​Mesuva

Full Changelog: surjithctly/astro-navbar@v2.3.7...v2.3.8

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.