Bump @astrojs/sitemap from 3.3.1 to 3.4.0#48

Bumps [@astrojs/sitemap](https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap) from 3.3.1 to 3.4.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases"><code>@​astrojs/sitemap</code>'s releases</a>.</em></p> <blockquote> <h2><code>@​astrojs/sitemap</code><a href="https://github.com/3"><code>@​3</code></a>.4.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/13753">#13753</a> <a href="https://github.com/withastro/astro/commit/90293de03320da51965f05cfa6923cbe5521f519"><code>90293de</code></a> Thanks <a href="https://github.com/mattyoho"><code>@​mattyoho</code></a>! - Customize the filenames of sitemap XML files generated by the <code>@astro/sitemap</code> integration by setting <code>filenameBase</code> in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.</p> <p>Generated sitemap files will appear at <code>/sitemap-0.xml</code> and <code>/sitemap-index.xml</code> by default, which may conflict with preexisting files. Set <code>filenameBase</code> to a custom value to avoid that if so:</p> <pre lang="js"><code>import { defineConfig } from 'astro/config'; import sitemap from '@astrojs/sitemap'; <p>export default defineConfig({ site: '<a href="https://example.com">https://example.com</a>', integrations: [ sitemap({ filenameBase: 'astronomy-sitemap', }), ], }); </code></pre></p> <p>This will yield sitemap and index files as <code>https://example.com/astronomy-sitemap-0.xml</code> and <code>https://example.com/astronomy-sitemap-index.xml</code>.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/integrations/sitemap/CHANGELOG.md"><code>@​astrojs/sitemap</code>'s changelog</a>.</em></p> <blockquote> <h2>3.4.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/13753">#13753</a> <a href="https://github.com/withastro/astro/commit/90293de03320da51965f05cfa6923cbe5521f519"><code>90293de</code></a> Thanks <a href="https://github.com/mattyoho"><code>@​mattyoho</code></a>! - Customize the filenames of sitemap XML files generated by the <code>@astro/sitemap</code> integration by setting <code>filenameBase</code> in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.</p> <p>Generated sitemap files will appear at <code>/sitemap-0.xml</code> and <code>/sitemap-index.xml</code> by default, which may conflict with preexisting files. Set <code>filenameBase</code> to a custom value to avoid that if so:</p> <pre lang="js"><code>import { defineConfig } from 'astro/config'; import sitemap from '@astrojs/sitemap'; <p>export default defineConfig({ site: '<a href="https://example.com">https://example.com</a>', integrations: [ sitemap({ filenameBase: 'astronomy-sitemap', }), ], }); </code></pre></p> <p>This will yield sitemap and index files as <code>https://example.com/astronomy-sitemap-0.xml</code> and <code>https://example.com/astronomy-sitemap-index.xml</code>.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/2ba4692792954ea612161e3bd8aa4515e2169b57"><code>2ba4692</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap/issues/13771">#13771</a>)</li> <li><a href="https://github.com/withastro/astro/commit/90293de03320da51965f05cfa6923cbe5521f519"><code>90293de</code></a> Add a config option for filenames generated by the <code>@​astrojs/sitemap</code> integrati...</li> <li>See full diff in <a href="https://github.com/withastro/astro/commits/@astrojs/[email protected]/packages/integrations/sitemap">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>