Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.5.0

Minor Changes

• #13682 5824b32 Thanks @​gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

  This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

  The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

  Example:

  import { defineConfig } from 'astro/config';
  import sitemap from '@astrojs/sitemap';
  export default defineConfig({
  site: 'https://example.com',
  integrations: [
  sitemap({
  customSitemaps: [
  'https://example.com/blog/sitemap.xml',
  'https://example.com/helpcenter/sitemap.xml',
  ],
  }),
  ],
  });

  Learn more in the @astrojs/sitemap configuration documentation.

Sourced from @​astrojs/sitemap's changelog.

3.5.0

Minor Changes

• #13682 5824b32 Thanks @​gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

  This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

  The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

  Example:

  import { defineConfig } from 'astro/config';
  import sitemap from '@astrojs/sitemap';
  export default defineConfig({
  site: 'https://example.com',
  integrations: [
  sitemap({
  customSitemaps: [
  'https://example.com/blog/sitemap.xml',
  'https://example.com/helpcenter/sitemap.xml',
  ],
  }),
  ],
  });

  Learn more in the @astrojs/sitemap configuration documentation.

• a186848 [ci] release (#14217)
• cad3cc6 [ci] format
• 5824b32 feat(@​astro/sitemap): custom sitemaps (#13682)
• See full diff in compare view

Sourced from astro's releases.

astro@5.13.2

Patch Changes

• 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

• Updated dependencies [4d16de7]:

  • @​astrojs/internal-helpers@​0.7.2
  • @​astrojs/markdown-remark@​6.3.6

astro@5.13.1

Patch Changes

• #14225 f2490ab Thanks @​delucis! - Fixes the experimental.chromeDevtoolsWorkspace feature.

astro@5.13.0

Minor Changes

• #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

  However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

  The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

  Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

  To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

  // astro.config.mjs
  import { defineConfig } from "astro/config";
  export default defineConfig({
  
  experimental: {
  staticImportMetaEnv: true
  
  
  rawEnvValues: false
  
  
  }
  });

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;

... (truncated)

Sourced from astro's changelog.

5.13.2

Patch Changes

• 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

• Updated dependencies [4d16de7]:

  • @​astrojs/internal-helpers@​0.7.2
  • @​astrojs/markdown-remark@​6.3.6

5.13.1

Patch Changes

• #14225 f2490ab Thanks @​delucis! - Fixes the experimental.chromeDevtoolsWorkspace feature.

5.13.0

Minor Changes

• #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

  Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

  However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

  The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

  Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

  The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

  To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

  // astro.config.mjs
  import { defineConfig } from "astro/config";
  export default defineConfig({
  
  experimental: {
  staticImportMetaEnv: true
  
  
  rawEnvValues: false
  
  
  }
  });

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

... (truncated)

• 9288133 [ci] release (#14232)
• 1040510 [ci] format
• 4d16de7 Merge commit from fork
• 1591bc7 [ci] release (#14227)
• f2490ab Fix automatic Chrome DevTools workspace feature (#14225)
• a186848 [ci] release (#14217)
• b33780d [ci] format
• 39911b8 feat: experimental static import.meta.env (#14173)
• 41ed3ac feat: add automatic chrome workspace handling (#14122)
• 806d2dc chore: add additional contributor to changelog (#14203)
• See full diff in compare view

Sourced from @​biomejs/biome's releases.

Biome CLI v2.2.0

2.2.0

Minor Changes

• #5506 1f8755b Thanks @​sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

  You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.

  {
    "options": {
      "patterns": [
        {
          "group": ["import-foo/*", "!import-foo/baz"],
          "message": "import-foo is deprecated, except for modules in import-foo/baz."
        }
      ]
    }
  }

  Invalid examples

  import foo from "import-foo/foo";
  import bar from "import-foo/bar";

  Valid examples

  import baz from "import-foo/baz";

  Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions. The following example restricts the import names that match x , y or z letters from modules under import-foo/.

  {
    "options": {
      "patterns": [
        {
          "group": ["import-foo/*"],
          "importNamePattern": "[xyz]"
        }
      ]
    }
  }

... (truncated)

Sourced from @​biomejs/biome's changelog.

2.2.0

Minor Changes

• #5506 1f8755b Thanks @​sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

  You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.

  {
    "options": {
      "patterns": [
        {
          "group": ["import-foo/*", "!import-foo/baz"],
          "message": "import-foo is deprecated, except for modules in import-foo/baz."
        }
      ]
    }
  }

  Invalid examples

  import foo from "import-foo/foo";
  import bar from "import-foo/bar";

  Valid examples

  import baz from "import-foo/baz";

  Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions. The following example restricts the import names that match x , y or z letters from modules under import-foo/.

  {
    "options": {
      "patterns": [
        {
          "group": ["import-foo/*"],
          "importNamePattern": "[xyz]"
        }
      ]
    }
  }

... (truncated)

• e1ba03c chore: restore version and use different runner
• 1b783c8 chore: revert version
• ee7ec19 chore: update version and lockfile
• 9b3ff65 chore: revert version
• 5b6c6ed ci: release (#7157)
• 0667478 chore: fix various typos across codebase (#7216)
• f66209b chore: fix typos in biome formatter and grit crates (#7207)
• a3840ac Merge pull request #7167 from biomejs/next
• 13bbbc1 chore: add Vercel to sponsors (#7200)
• 7d00fdd [autofix.ci] apply automated fixes
• Additional commits viewable in compare view

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