chore(deps): update dependency astro to v5.16.15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
astro (source)	5.16.12 → 5.16.15

---

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.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Cross File	✅

Access your configuration settings here.

​