Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2023

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/sitemap (source) 3.0.4 -> 3.6.0 age confidence
@astrojs/tailwind (source) 5.1.0 -> 5.1.5 age confidence
astro (source) 4.0.8 -> 4.16.19 age confidence
sharp (source, changelog) ^0.33.1 -> ^0.34.0 age confidence
tailwindcss (source) 3.4.0 -> 3.4.19 age confidence

Release Notes

withastro/astro (@​astrojs/sitemap)

v3.6.0

Compare Source

Minor Changes
  • #​14285 bedc31b Thanks @​jdcolombo! - Adds a new configuration option namespaces for more control over XML namespaces used in sitemap generation

    Excluding unused namespaces can help create cleaner, more focused sitemaps that are faster for search engines to parse and use less bandwidth. If your site doesn't have news content, videos, or multiple languages, you can exclude those namespaces to reduce XML bloat.

    The namespaces option allows you to configure news, xhtml, image, and video namespaces independently. All namespaces are enabled by default for backward compatibility and no change to existing projects is necessary. But now, you can choose to streamline your XML and avoid unnecessary code.

    For example, to exclude the video namespace from your sitemap, set video: false in your configuration:

    // astro.config.mjs
    import { sitemap } from '@​astrojs/sitemap';
    
    export default {
      integrations: [
        sitemap({
          namespaces: {
            video: false,
            // other namespaces remain enabled by default
          }
        })
      ]
    };
    

    The generated XML will not include the xmlns:video namespace:

    <?xml version="1.0" encoding="UTF-8"?>
    <urlset
      xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
      xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
      xmlns:xhtml="http://www.w3.org/1999/xhtml"
      xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
    >
      <!-- ... -->
    </urlset>
    

v3.5.1

Compare Source

Patch Changes
  • #​14233 896886c Thanks @​gouravkhunger! - Fixes the issue with the option lastmod where if it is defined it applies correctly to <url> entries in each sitemap-${i}.xml file but not the <sitemap> entries in the root sitemap-index.xml file.

v3.5.0

Compare Source

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 '@&#8203;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.

v3.4.2

Compare Source

Patch Changes

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes
  • #​13753 90293de Thanks @​mattyoho! - Customize the filenames of sitemap XML files generated by the @astro/sitemap integration by setting filenameBase in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.

    Generated sitemap files will appear at /sitemap-0.xml and /sitemap-index.xml by default, which may conflict with preexisting files. Set filenameBase to a custom value to avoid that if so:

    import { defineConfig } from 'astro/config';
    import sitemap from '@&#8203;astrojs/sitemap';
    
    export default defineConfig({
      site: 'https://example.com',
      integrations: [
        sitemap({
          filenameBase: 'astronomy-sitemap',
        }),
      ],
    });

    This will yield sitemap and index files as https://example.com/astronomy-sitemap-0.xml and https://example.com/astronomy-sitemap-index.xml.

v3.3.1

Patch Changes

v3.3.0

Minor Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes

v3.1.6

Compare Source

Patch Changes

v3.1.5

Compare Source

Patch Changes

v3.1.4

Compare Source

Patch Changes

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes
  • #​9846 9b78c992750cdb99c40a89a00ea2a0d1c00877d7 Thanks @​ktym4a! - Adds a new configuration option prefix that allows you to change the default sitemap-*.xml file name.

    By default, running astro build creates both sitemap-index.xml and sitemap-0.xml in your output directory.

    To change the names of these files (e.g. to astrosite-index.xml and astrosite-0.xml), set the prefix option in your sitemap integration configuration:

    import { defineConfig } from 'astro/config';
    import sitemap from '@&#8203;astrojs/sitemap';
    export default defineConfig({
      site: 'https://example.com',
      integrations: [
        sitemap({
          prefix: 'astrosite-',
        }),
      ],
    });
    

    This option is useful when Google Search Console is unable to fetch your default sitemap files, but can read renamed files.

v3.0.5

Compare Source

Patch Changes
withastro/astro (@​astrojs/tailwind)

v5.1.5

Compare Source

Patch Changes

v5.1.4

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes
withastro/astro (astro)

v4.16.19

Compare Source

Patch Changes

v4.16.18

Compare Source

Patch Changes

v4.16.17

Compare Source

Patch Changes

v4.16.16

Compare Source

Patch Changes

v4.16.15

Compare Source

Patch Changes

v4.16.14

Compare Source

Patch Changes

v4.16.13

Compare Source

Patch Changes
  • #​12436 453ec6b Thanks @​martrapp! - Fixes a potential null access in the clientside router

  • #​12392 0462219 Thanks @​apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the same entrypoint and different pattern

v4.16.12

Compare Source

Patch Changes
  • #​12420 acac0af Thanks @​ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a valid Response.

v4.16.11

Compare Source

Patch Changes
  • #​12305 f5f7109 Thanks @​florian-lefebvre! - Fixes a case where the error overlay would not escape the message

  • #​12402 823e73b Thanks @​ematipico! - Fixes a case where Astro allowed to call an action without using Astro.callAction. This is now invalid, and Astro will show a proper error.

    ---
    import { actions } from "astro:actions";
    
    -const result = actions.getUser({ userId: 123 });
    +const result = Astro.callAction(actions.getUser, { userId: 123 });
    ---
  • #​12401 9cca108 Thanks @​bholmesdev! - Fixes unexpected 200 status in dev server logs for action errors and redirects.

v4.16.10

Compare Source

Patch Changes

v4.16.9

Compare Source

Patch Changes

v4.16.8

Compare Source

Patch Changes

v4.16.7

Compare Source

Patch Changes

v4.16.6

Compare Source

Patch Changes
  • #​11823 a3d30a6 Thanks @​DerTimonius! - fix: improve error message when inferSize is used in local images with the Image component

  • #​12227 8b1a641 Thanks @​florian-lefebvre! - Fixes a case where environment variables would not be refreshed when using astro:env

  • #​12239 2b6daa5 Thanks @​ematipico! - BREAKING CHANGE to the experimental Container API only

    Changes the default page rendering behavior of Astro components in containers, and adds a new option partial: false to render full Astro pages as before.

    Previously, the Container API was rendering all Astro components as if they were full Astro pages containing <!DOCTYPE html> by default. This was not intended, and now by default, all components will render as page partials: only the contents of the components without a page shell.

    To render the component as a full-fledged Astro page, pass a new option called partial: false to renderToString() and renderToResponse():

    import { experimental_AstroContainer as AstroContainer } from 'astro/container';
    import Card from '../src/components/Card.astro';
    
    const container = AstroContainer.create();
    
    await container.renderToString(Card); // the string will not contain `<!DOCTYPE html>`
    await container.renderToString(Card, { partial: false }); // the string will contain `<!DOCTYPE html>`

v4.16.5

Compare Source

Patch Changes

v4.16.4

Compare Source

Patch Changes
  • #​12223 79ffa5d Thanks @​ArmandPhilippot! - Fixes a false positive reported by the dev toolbar Audit app where a label was considered missing when associated with a button

    The button element can be used with a label (e.g. to create a switch) and should not be reported as an accessibility issue when used as a child of a label.

  • #​12199 c351352 Thanks @​ematipico! - Fixes a regression in the computation of Astro.currentLocale

  • #​12222 fb55695 Thanks @​ematipico! - Fixes an issue where the edge middleware couldn't correctly compute the client IP address when calling ctx.clientAddress()

v4.16.3

Compare Source

Patch Changes

v4.16.2

Compare Source

Patch Changes

v4.16.1

Compare Source

Patch Changes
  • #​12177 a4ffbfa Thanks @​matthewp! - Ensure we target scripts for execution in the router

    Using document.scripts is unsafe because if the application has a name="scripts" this will shadow the built-in document.scripts. Fix is to use getElementsByTagName to ensure we're only grabbing real scripts.

  • #​12173 2d10de5 Thanks @​ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.

v4.16.0

Compare Source

Minor Changes
  • #​12039 710a1a1 Thanks @​ematipico! - Adds a markdown.shikiConfig.langAlias option that allows aliasing a non-supported code language to a known language. This is useful when the language of your code samples is not a built-in Shiki language, but you want your Markdown source to contain an accurate language while also displaying syntax highlighting.

    The following example configures Shiki to highlight cjs code blocks using the javascript syntax highlighter:

    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      markdown: {
        shikiConfig: {
          langAlias: {
            cjs: 'javascript',
          },
        },
      },
    });

    Then in your Markdown, you can use the alias as the language for a code block for syntax highlighting:

    ```cjs
    'use strict';
    
    function commonJs() {
      return 'I am a commonjs file';
    }
    ```
  • #​11984 3ac2263 Thanks @​chaegumi! - Adds a new build.concurreny configuration option to specify the number of pages to build in parallel

    In most cases, you should not change the default value of 1.

    Use this option only when other attempts to reduce the overall rendering time (e.g. batch or cache long running tasks like fetch calls or data access) are not possible or are insufficient.

    Use this option only if the refactors are not possible. If the number is set too high, the page rendering may slow down due to insufficient memory resources and because JS is single-threaded.

    [!WARNING]
    This feature is stable and is not considered experimental. However, this feature is only intended to address difficult performance issues, and breaking changes may occur in a minor release to keep this option as performant as possible.

    // astro.config.mjs
    import { defineConfig } from 'astro';
    
    export default defineConfig({
      build: {
        concurrency: 2,
      },
    });
Patch Changes
  • #​12160 c6fd1df Thanks @​louisescher! - Fixes a bug where astro.config.mts and astro.config.cts weren't reloading the dev server upon modifications.

  • #​12130 e96bcae Thanks @​thehansys! - Fixes a bug in the parsing of x-forwarded-\* Request headers, where multiple values assigned to those headers were not correctly parsed.

    Now, headers like x-forwarded-proto: https,http are correctly parsed.

  • #​12147 9db755a Thanks @​ascorbic! - Skips setting statusMessage header for HTTP/2 response

    HTTP/2 doesn't support status message, so setting this was logging a warning.

  • #​12151 bb6d37f Thanks @​ematipico! - Fixes an issue where Astro.currentLocale wasn't incorrectly computed when the defaultLocale belonged to a custom locale path.

  • Updated dependencies [710a1a1]:

v4.15.12

Compare Source

Patch Changes

v4.15.11

Compare Source

Patch Changes
  • #​12097 11d447f Thanks @​ascorbic! - Fixes error where references in content layer schemas sometimes incorrectly report as missing

  • #​12108 918953b Thanks @​lameuler! - Fixes a bug where data URL images were not correctly handled. The bug resulted in an ENAMETOOLONG error.

  • #​12105 42037f3 Thanks @​ascorbic! - Returns custom statusText that has been set in a Response

  • #​12109 ea22558 Thanks @​ematipico! - Fixes a regression that was introduced by an internal refactor of how the middleware is loaded by the Astro application. The regression was introduced by #​11550.

    When the edge middleware feature is opted in, Astro removes the middleware function from the SSR manifest, and this wasn't taken into account during the refactor.

  • #​12106 d3a74da Thanks @​ascorbic! - Handles case where an immutable Response object is returned from an endpoint

  • #​12090 d49a537 Thanks @​markjaquith! - Server islands: changes the server island HTML placeholder comment so that it is much less likely to get removed by HTML minifiers.

v4.15.10

Compare Source

Patch Changes

v4.15.9

Compare Source

Patch Changes
  • #​12034 5b3ddfa Thanks @​ematipico! - Fixes an issue where the middleware wasn't called when a project uses 404.astro.

  • #​12042 243ecb6 Thanks @​ematipico! - Fixes a problem in the Container API, where a polyfill wasn't correctly applied. This caused an issue in some environments where crypto isn't supported.

  • #​12038 26ea5e8 Thanks @​ascorbic! - Resolves image paths in content layer with initial slash as project-relative

    When using the image() schema helper, previousl


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Apr 25, 2023

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
astro-starter-tailwindcss Error Error Dec 10, 2025 8:25pm

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9b9f31a to 9b61631 Compare April 26, 2023 02:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9b61631 to dff1fe9 Compare April 27, 2023 12:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from dff1fe9 to 15121b9 Compare April 27, 2023 18:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 15121b9 to 3e4656a Compare April 28, 2023 00:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3e4656a to 336acf2 Compare May 1, 2023 15:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 336acf2 to aaf3943 Compare May 2, 2023 19:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from aaf3943 to d3c824d Compare May 3, 2023 09:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d3c824d to b9cc06c Compare May 4, 2023 11:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b9cc06c to 4f364b6 Compare May 4, 2023 18:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4f364b6 to 4c67448 Compare May 4, 2023 22:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4c67448 to 6c2ebce Compare May 5, 2023 19:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6c2ebce to e7065c5 Compare May 8, 2023 12:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e7065c5 to f8faed7 Compare May 8, 2023 21:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f8faed7 to bd1456e Compare May 9, 2023 22:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9796085 to 1079cea Compare August 13, 2025 16:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1079cea to 710c68e Compare August 14, 2025 11:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 710c68e to 5a46cc4 Compare August 19, 2025 18:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5a46cc4 to 9f2c20e Compare August 22, 2025 19:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9f2c20e to e693989 Compare August 31, 2025 10:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e693989 to 945dff8 Compare September 19, 2025 15:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 945dff8 to c8aa4de Compare September 25, 2025 15:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c8aa4de to fbcce1a Compare October 1, 2025 20:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fbcce1a to 171a77c Compare October 21, 2025 17:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 171a77c to 0fa6a9d Compare November 6, 2025 18:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0fa6a9d to fbd94b2 Compare November 10, 2025 23:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fbd94b2 to fc13be5 Compare November 19, 2025 00:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fc13be5 to 43df3a1 Compare December 3, 2025 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant