Bump astro from 5.16.12 to 5.16.14 in the astro group

[dependabot]

Bumps the astro group with 1 update: astro.

Updates astro from 5.16.12 to 5.16.14

Release notes

Sourced from astro's releases.

astro@5.16.14

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:

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.14

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:

... (truncated)

Commits

• f7a8415 [ci] release (#15278)
• 7db2fda address sarah's feedback (#15280)
• c775fce feat(fonts)!: local provider unification (#15213)
• edabeaa fix(cli): add .vercel to .gitignore when using astro add vercel (#15185)
• ce0c346 [ci] release (#15270)
• 60d1045 clear fonts test cache (#15274)
• c4a15a8 [ci] format
• cb60ee1 feat(fonts): getFontBuffer() (#15182)
• d14dfc2 Add a --db-app-token flag to "astro db" execute, push, and verify commands (#...
• See full diff 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