fix(deps): update dependency astro to v4.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
astro (source)	4.13.4 -> 4.14.0

---

Release Notes

withastro/astro (astro)

v4.14.0

Compare Source

Minor Changes

• #​11657 a23c69d Thanks @​bluwy! - Deprecates the option for route-generating files to export a dynamic value for prerender. Only static values are now supported (e.g. export const prerender = true or = false). This allows for better treeshaking and bundling configuration in the future.

  Adds a new "astro:route:setup" hook to the Integrations API to allow you to dynamically set options for a route at build or request time through an integration, such as enabling on-demand server rendering.

  To migrate from a dynamic export to the new hook, update or remove any dynamic prerender exports from individual routing files:

  // src/pages/blog/[slug].astro
  - export const prerender = import.meta.env.PRERENDER

  Instead, create an integration with the "astro:route:setup" hook and update the route's prerender option:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { loadEnv } from 'vite';
  
  export default defineConfig({
    integrations: [setPrerender()],
  });
  
  function setPrerender() {
    const { PRERENDER } = loadEnv(process.env.NODE_ENV, process.cwd(), '');
  
    return {
      name: 'set-prerender',
      hooks: {
        'astro:route:setup': ({ route }) => {
          if (route.component.endsWith('/blog/[slug].astro')) {
            route.prerender = PRERENDER;
          }
        },
      },
    };
  }

• #​11360 a79a8b0 Thanks @​ascorbic! - Adds a new injectTypes() utility to the Integration API and refactors how type generation works

  Use injectTypes() in the astro:config:done hook to inject types into your user's project by adding a new a *.d.ts file.

  The filename property will be used to generate a file at /.astro/integrations/<normalized_integration_name>/<normalized_filename>.d.ts and must end with ".d.ts".

  The content property will create the body of the file, and must be valid TypeScript.

  Additionally, injectTypes() returns a URL to the normalized path so you can overwrite its content later on, or manipulate it in any way you want.

  // my-integration/index.js
  export default {
    name: 'my-integration',
    'astro:config:done': ({ injectTypes }) => {
      injectTypes({
        filename: 'types.d.ts',
        content: "declare module 'virtual:my-integration' {}",
      });
    },
  };

  Codegen has been refactored. Although src/env.d.ts will continue to work as is, we recommend you update it:

  - /// <reference types="astro/client" />
  + /// <reference path="../.astro/types.d.ts" />
  - /// <reference path="../.astro/env.d.ts" />
  - /// <reference path="../.astro/actions.d.ts" />

• #​11605 d3d99fb Thanks @​jcayzac! - Adds a new property meta to Astro's built-in <Code /> component.

  This allows you to provide a value for Shiki's meta attribute to pass options to transformers.

  The following example passes an option to highlight lines 1 and 3 to Shiki's tranformerMetaHighlight:

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

[coderabbitai]

Walkthrough

The update in the package.json file reflects a version bump of the astro dependency from 4.13.4 to 4.14.0. This change suggests potential enhancements, including new features, improvements, or bug fixes that could enhance the functionality of the application. To fully understand the implications, a review of the release notes for astro will provide detailed insights into the specific changes introduced.

Changes

File	Change Summary
package.json	Updated astro dependency version from 4.13.4 to 4.14.0

Poem

In the garden of code where the updates bloom,
A hop, skip, and jump brings a new light to the room. 🌼
With astro now gleaming, its features take flight,
Bugs disappear softly, like dreams in the night.
So let's cheer for the changes, let joy take its place,
For every new version, a smile on our face! 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[tatsutakeinjp-bot]

Device	URL
mobile	https://9b56842d.asis-quest.pages.dev

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cb0d577 and 85dfec6.

Files ignored due to path filters (1)

• bun.lockb is excluded by !**/bun.lockb

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

26-26: Verify compatibility with Astro v4.14.0.

The astro dependency has been updated from version 4.13.4 to 4.14.0. Ensure that the new version is compatible with your existing codebase and does not introduce any breaking changes. Consider reviewing the release notes for any deprecated features or new functionalities that might affect your application.