Bump astro from 4.11.3 to 4.12.0

[dependabot]

Bumps astro from 4.11.3 to 4.12.0.

Release notes

Sourced from astro's releases.

astro@4.12.0

Minor Changes

• #11341 49b5145 Thanks @​madcampos! - Adds support for Shiki's defaultColor option.

  This option allows you to override the values of a theme's inline style, adding only CSS variables to give you more flexibility in applying multiple color themes.

  Configure defaultColor: false in your Shiki config to apply throughout your site, or pass to Astro's built-in <Code> component to style an individual code block.

  import { defineConfig } from 'astro/config';
  export default defineConfig({
    markdown: {
      shikiConfig: {
        themes: {
          light: 'github-light',
          dark: 'github-dark',
        },
        defaultColor: false,
      },
    },
  });

  ---
  import { Code } from 'astro:components';
  ---
  <Code code={const useMyColors = true} lang="js" defaultColor={false} />

• #11304 2e70741 Thanks @​Fryuni! - Refactors the type for integration hooks so that integration authors writing custom integration hooks can now allow runtime interactions between their integration and other integrations.

  This internal change should not break existing code for integration authors.

  To declare your own hooks for your integration, extend the Astro.IntegrationHooks interface:

  // your-integration/types.ts
  declare global {
    namespace Astro {
      interface IntegrationHooks {
        'myLib:eventHappened': (your: string, parameters: number) => Promise<void>;
      }
    }
  }

  Call your hooks on all other integrations installed in a project at the appropriate time. For example, you can call your hook on initialization before either the Vite or Astro config have resolved:

... (truncated)

Changelog

Sourced from astro's changelog.

4.12.0

Minor Changes

• #11341 49b5145 Thanks @​madcampos! - Adds support for Shiki's defaultColor option.

  This option allows you to override the values of a theme's inline style, adding only CSS variables to give you more flexibility in applying multiple color themes.

  Configure defaultColor: false in your Shiki config to apply throughout your site, or pass to Astro's built-in <Code> component to style an individual code block.

  import { defineConfig } from 'astro/config';
  export default defineConfig({
    markdown: {
      shikiConfig: {
        themes: {
          light: 'github-light',
          dark: 'github-dark',
        },
        defaultColor: false,
      },
    },
  });

  ---
  import { Code } from 'astro:components';
  ---
  <Code code={const useMyColors = true} lang="js" defaultColor={false} />

• #11304 2e70741 Thanks @​Fryuni! - Refactors the type for integration hooks so that integration authors writing custom integration hooks can now allow runtime interactions between their integration and other integrations.

  This internal change should not break existing code for integration authors.

  To declare your own hooks for your integration, extend the Astro.IntegrationHooks interface:

  // your-integration/types.ts
  declare global {
    namespace Astro {
      interface IntegrationHooks {
        'myLib:eventHappened': (your: string, parameters: number) => Promise<void>;
      }
    }
  }

... (truncated)

Commits

• aa05be3 [ci] release (#11481)
• a637169 [ci] format
• fe3afeb Fix Server Islands in Vercel (#11491)
• 1a26c6d [ci] format
• 061f1f4 fix: make root serializable (#11489)
• 7c9ed71 feat: noSync flag for astro check (#11482)
• e7bfbf8 [ci] format
• ca969d5 fix: incorrect astro:env runtime error (#11479)
• 34f9c25 fix: pin boxen to avoid JSON import (#11483)
• e67dcde [ci] format
• 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 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)