build(deps): bump astro from 4.12.3 to 4.13.0 in the astro group

[dependabot[bot]]

Bumps the astro group with 1 update: astro.

Updates astro from 4.12.3 to 4.13.0

Release notes

Sourced from astro's releases.

astro@4.13.0

Minor Changes

• #11507 a62345f Thanks @​ematipico! - Adds color-coding to the console output during the build to highlight slow pages.

  Pages that take more than 500 milliseconds to render will have their build time logged in red. This change can help you discover pages of your site that are not performant and may need attention.

• #11379 e5e2d3e Thanks @​alexanderniebuhr! - The experimental.contentCollectionJsonSchema feature introduced behind a flag in v4.5.0 is no longer experimental and is available for general use.

  If you are working with collections of type data, Astro will now auto-generate JSON schema files for your editor to get IntelliSense and type-checking. A separate file will be created for each data collection in your project based on your collections defined in src/content/config.ts using a library called zod-to-json-schema.

  This feature requires you to manually set your schema's file path as the value for $schema in each data entry file of the collection:

  {
    "$schema": "../../../.astro/collections/authors.schema.json",
    "name": "Armand",
    "skills": ["Astro", "Starlight"]
  }
  

  Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's json.schemas setting, provide the path of files to match and the location of your JSON schema:

  {
    "json.schemas": [
      {
        "fileMatch": ["/src/content/authors/**"],
        "url": "./.astro/collections/authors.schema.json"
      }
    ]
  }
  

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  export default defineConfig({
  
  experimental: {
  contentCollectionJsonSchema: true
  }
  })
  

If you have been waiting for stabilization before using JSON Schema generation for content collections, you can now do so.

Please see the content collections guide for more about this feature.

... (truncated)

Changelog

Sourced from astro's changelog.

4.13.0

Minor Changes

• #11507 a62345f Thanks @​ematipico! - Adds color-coding to the console output during the build to highlight slow pages.

  Pages that take more than 500 milliseconds to render will have their build time logged in red. This change can help you discover pages of your site that are not performant and may need attention.

• #11379 e5e2d3e Thanks @​alexanderniebuhr! - The experimental.contentCollectionJsonSchema feature introduced behind a flag in v4.5.0 is no longer experimental and is available for general use.

  If you are working with collections of type data, Astro will now auto-generate JSON schema files for your editor to get IntelliSense and type-checking. A separate file will be created for each data collection in your project based on your collections defined in src/content/config.ts using a library called zod-to-json-schema.

  This feature requires you to manually set your schema's file path as the value for $schema in each data entry file of the collection:

  {
    "$schema": "../../../.astro/collections/authors.schema.json",
    "name": "Armand",
    "skills": ["Astro", "Starlight"]
  }
  

  Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's json.schemas setting, provide the path of files to match and the location of your JSON schema:

  {
    "json.schemas": [
      {
        "fileMatch": ["/src/content/authors/**"],
        "url": "./.astro/collections/authors.schema.json"
      }
    ]
  }
  

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  export default defineConfig({
  
  experimental: {
  contentCollectionJsonSchema: true
  }
  })
  

If you have been waiting for stabilization before using JSON Schema generation for content collections, you can now do so.

Please see the content collections guide for more about this feature.

... (truncated)

Commits

• 4474887 [ci] release (#11578)
• 6aaeec5 Update errors-data.ts for Astro.rewrite release in 4.13 (#11580)
• 750d532 fix(deps): update all non-major dependencies (#11565)
• 45ad326 feat: stabilise the rewrite APIs (#11542)
• a62345f feat: log slow pages in red (#11507)
• 2cf770d [ci] format
• e5e2d3e chore: unflag contentCollectionJsonSchema (#11379)
• 60b2766 Verify you can use server:defer on self-imported module (#11577)
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions