build(deps): bump the astro-packages group with 3 updates

[dependabot]

Bumps the astro-packages group with 3 updates: @astrojs/rss, @astrojs/sitemap and astro.

Updates @astrojs/rss from 4.0.14 to 4.0.15

Release notes

Sourced from @​astrojs/rss's releases.

@​astrojs/rss@​4.0.15

Patch Changes

• #15199 d8e64ef Thanks @​ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.

@​astrojs/rss@​4.0.15-beta.2

Patch Changes

• #15283 daf41c6 Thanks @​eldair! - Updates validation to use Zod v4

@​astrojs/rss@​4.0.15-beta.1

Patch Changes

• #15187 bbb5811 Thanks @​matthewp! - Update to Astro 6 beta

@​astrojs/rss@​4.0.15-alpha.0

Patch Changes

• #14956 0ff51df Thanks @​matthewp! - Updates usage of zod to own dependency rather than relying on astro/zod

Changelog

Sourced from @​astrojs/rss's changelog.

4.0.15

Patch Changes

• #15199 d8e64ef Thanks @​ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.

Commits

• 44f4e78 [ci] release (#15188)
• d8e64ef fix(docs): replace outdated Astro docs links (#15199)
• 718f5e1 fix(deps): update all non-major dependencies (#15072)
• 3805e65 fix(deps): update all non-major dependencies (#14707)
• See full diff in compare view

Updates @astrojs/sitemap from 3.6.0 to 3.7.0

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.7.0

Minor Changes

• #14471 4296373 Thanks @​Slackluky! - Adds the ability to split sitemap generation into chunks based on customizable logic. This allows for better management of large sitemaps and improved performance. The new chunks option in the sitemap configuration allows users to define functions that categorize sitemap items into different chunks. Each chunk is then written to a separate sitemap file.

  integrations: [
    sitemap({
      serialize(item) { th
        return item
      },
      chunks: { // this property will be treated last on the configuration
        'blog': (item) => {  // will produce a sitemap file with `blog` name (sitemap-blog-0.xml)
          if (/blog/.test(item.url)) { // filter path that will be included in this specific sitemap file
            item.changefreq = 'weekly';
            item.lastmod = new Date();
            item.priority = 0.9; // define specific properties for this filtered path
            return item;
          }
        },
        'glossary': (item) => {
          if (/glossary/.test(item.url)) {
            item.changefreq = 'weekly';
            item.lastmod = new Date();
            item.priority = 0.7;
            return item;
          }
        }
    // the rest of the path will be stored in `sitemap-pages.0.xml`
  },
  
  }),
  ],
  

@​astrojs/sitemap@​3.6.1

Patch Changes

• #15033 dd06779 Thanks @​florian-lefebvre! - Updates how routes are retrieved to avoid relying on a deprecated API

@​astrojs/sitemap@​3.6.1-beta.2

Patch Changes

• #15187 bbb5811 Thanks @​matthewp! - Update to Astro 6 beta

@​astrojs/sitemap@​3.6.1-alpha.1

Patch Changes

• #15036 f125a73 Thanks @​florian-lefebvre! - Updates how routes are retrieved to avoid relying on a deprecated API

... (truncated)

Changelog

Sourced from @​astrojs/sitemap's changelog.

3.7.0

Minor Changes

• #14471 4296373 Thanks @​Slackluky! - Adds the ability to split sitemap generation into chunks based on customizable logic. This allows for better management of large sitemaps and improved performance. The new chunks option in the sitemap configuration allows users to define functions that categorize sitemap items into different chunks. Each chunk is then written to a separate sitemap file.

  integrations: [
    sitemap({
      serialize(item) { th
        return item
      },
      chunks: { // this property will be treated last on the configuration
        'blog': (item) => {  // will produce a sitemap file with `blog` name (sitemap-blog-0.xml)
          if (/blog/.test(item.url)) { // filter path that will be included in this specific sitemap file
            item.changefreq = 'weekly';
            item.lastmod = new Date();
            item.priority = 0.9; // define specific properties for this filtered path
            return item;
          }
        },
        'glossary': (item) => {
          if (/glossary/.test(item.url)) {
            item.changefreq = 'weekly';
            item.lastmod = new Date();
            item.priority = 0.7;
            return item;
          }
        }
    // the rest of the path will be stored in `sitemap-pages.0.xml`
  },
  
  }),
  ],
  

3.6.1

Patch Changes

• #15033 dd06779 Thanks @​florian-lefebvre! - Updates how routes are retrieved to avoid relying on a deprecated API

Commits

• 44f4e78 [ci] release (#15188)
• 220b979 [ci] format
• 4296373 Feature(sitemap): named files chunking strategy (#14471)
• e73deb8 [ci] release (#15031)
• dd06779 chore(sitemap): migrate to astro:routes:resolved (#15033)
• 3805e65 fix(deps): update all non-major dependencies (#14707)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​astrojs/sitemap since your current version.

Updates astro from 5.16.6 to 5.17.1

Release notes

Sourced from astro's releases.

astro@5.17.1

Patch Changes

• #15334 d715f1f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Removes the getFontBuffer() helper function exported from astro:assets when using the experimental Fonts API

  This experimental feature introduced in v15.6.13 ended up causing significant memory usage during build. This feature has been removed and will be reintroduced after further exploration and testing.

  If you were relying on this function, you can replicate the previous behavior manually:

  • On prerendered routes, read the file using node:fs
  • On server rendered routes, fetch files using URLs from fontData and context.url

astro@5.17.0

Minor Changes

• #14932 b19d816 Thanks @​patrickarlt! - Adds support for returning a Promise from the parser() option of the file() loader

  This enables you to run asynchronous code such as fetching remote data or using async parsers when loading files with the Content Layer API.

  For example:

  import { defineCollection } from 'astro:content';
  import { file } from 'astro/loaders';
  const blog = defineCollection({
  loader: file('src/data/blog.json', {
  parser: async (text) => {
  const data = JSON.parse(text);
    // Perform async operations like fetching additional data
    const enrichedData = await fetch(`https://api.example.com/enrich`, {
      method: 'POST',
      body: JSON.stringify(data),
    }).then((res) => res.json());
  return enrichedData;
  },
  
  }),
  });
  export const collections = { blog };

  See the parser() reference documentation for more information.

• #15171 f220726 Thanks @​mark-ignacio! - Adds a new, optional kernel configuration option to select a resize algorithm in the Sharp image service

... (truncated)

Changelog

Sourced from astro's changelog.

5.17.1

Patch Changes

• #15334 d715f1f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Removes the getFontBuffer() helper function exported from astro:assets when using the experimental Fonts API

  This experimental feature introduced in v15.6.13 ended up causing significant memory usage during build. This feature has been removed and will be reintroduced after further exploration and testing.

  If you were relying on this function, you can replicate the previous behavior manually:

  • On prerendered routes, read the file using node:fs
  • On server rendered routes, fetch files using URLs from fontData and context.url

5.17.0

Minor Changes

• #14932 b19d816 Thanks @​patrickarlt! - Adds support for returning a Promise from the parser() option of the file() loader

  This enables you to run asynchronous code such as fetching remote data or using async parsers when loading files with the Content Layer API.

  For example:

  import { defineCollection } from 'astro:content';
  import { file } from 'astro/loaders';
  const blog = defineCollection({
  loader: file('src/data/blog.json', {
  parser: async (text) => {
  const data = JSON.parse(text);
    // Perform async operations like fetching additional data
    const enrichedData = await fetch(`https://api.example.com/enrich`, {
      method: 'POST',
      body: JSON.stringify(data),
    }).then((res) => res.json());
  return enrichedData;
  },
  
  }),
  });
  export const collections = { blog };

  See the parser() reference documentation for more information.

• #15171 f220726 Thanks @​mark-ignacio! - Adds a new, optional kernel configuration option to select a resize algorithm in the Sharp image service

... (truncated)

Commits

• 1c6c9fc [ci] release (#15339)
• d715f1f fix(fonts): remove getFontBuffer() (#15334)
• 08d38c6 [ci] release (#15325)
• 388818a [ci] format
• f1fce0e feat: add retainBody option to the glob() loader (#15022)
• 928529f adds ImageTransform.background (#15153)
• f220726 feat(sharp): add kernel option to image service config (#15171)
• b19d816 feat: allow for async parsing in file loader (#14932)
• 08e0fd7 Support partitioned cookies (#15063)
• 54f6006 Add devToolbar.placement configuration option (#15015)
• 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 <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