Skip to content
This repository was archived by the owner on Jun 12, 2025. It is now read-only.

Update astro monorepo #18

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update astro monorepo #18

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/cloudflare (source) 12.2.1 -> 12.5.4 age adoption passing confidence
@astrojs/mdx (source) 4.0.8 -> 4.3.0 age adoption passing confidence
@astrojs/partytown (source) 2.1.3 -> 2.1.4 age adoption passing confidence
@astrojs/preact (source) 4.0.4 -> 4.1.0 age adoption passing confidence
@astrojs/rss (source) 4.0.11 -> 4.0.12 age adoption passing confidence
@astrojs/sitemap (source) 3.2.1 -> 3.4.1 age adoption passing confidence
@astrojs/tailwind (source) 6.0.0 -> 6.0.2 age adoption passing confidence
astro (source) 5.2.5 -> 5.9.2 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/cloudflare)

v12.5.4

Compare Source

Patch Changes

v12.5.3

Compare Source

Patch Changes

v12.5.2

Compare Source

Patch Changes

v12.5.1

Compare Source

Patch Changes

v12.5.0

Compare Source

Minor Changes

  • #​13527 2fd6a6b Thanks @​ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

    Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:

v12.4.1

Compare Source

Patch Changes

v12.4.0

Compare Source

Minor Changes

  • #​13514 a9aafec Thanks @​ascorbic! - Automatically configures Cloudflare KV storage when experimental sessions are enabled

    If the experimental.session flag is enabled when using the Cloudflare adapter, Astro will automatically configure the session storage using the Cloudflare KV driver. You can still manually configure the session storage if you need to use a different driver or want to customize the session storage configuration. If you want to use sessions, you will need to create the KV namespace and declare it in your wrangler config. You can do this using the Wrangler CLI:

    npx wrangler kv namespace create SESSION

    This will log the id of the created namespace. You can then add it to your wrangler.json/wrangler.toml file like this:

    // wrangler.json
{
  "kv_namespaces": [
    {
      "binding": "SESSION",
      "id": "<your kv namespace id here>",
    },
  ],
}

    By default it uses the binding name SESSION, but if you want to use a different binding name you can do so by passing the sessionKVBindingName option to the adapter. For example:

    import { defineConfig } from 'astro/config';
import cloudflare from '@&#8203;astrojs/cloudflare';
export default defineConfig({
  output: 'server',
  site: `http://example.com`,
  adapter: cloudflare({
    platformProxy: {
      enabled: true,
    },
    sessionKVBindingName: 'MY_SESSION',
  }),
  experimental: {
    session: true,
  },
});

    See the Cloudflare KV docs for more details on setting up KV namespaces.

    See the experimental session docs for more information on configuring session storage.

Patch Changes

v12.3.1

Compare Source

Patch Changes

v12.3.0

Compare Source

Minor Changes
Patch Changes

v12.2.4

Compare Source

Patch Changes

v12.2.3

Compare Source

Patch Changes

v12.2.2

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

v4.3.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

v4.2.6

Compare Source

Patch Changes

v4.2.5

Compare Source

Patch Changes

v4.2.4

Compare Source

Patch Changes

v4.2.3

Compare Source

Patch Changes

v4.2.2

Patch Changes

v4.2.1

Patch Changes

v4.2.0

Compare Source

Minor Changes

  • #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

    By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
    special characters. This differs from the behavior of common Markdown processors.

    You can now disable this behavior with a new configuration flag:

    // astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    headingIdCompat: true,
  },
});

    This can be useful when heading IDs and anchor links need to behave consistently across your site
    and other platforms such as GitHub and npm.

    If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { rehypeHeadingIds } from '@&#8203;astrojs/markdown-remark';
import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';

export default defineConfig({
  markdown: {
    rehypePlugins: [
      [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
      otherPluginThatReliesOnHeadingIDs,
    ],
  },
});
Patch Changes

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes

  • #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

    Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

    Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

    No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

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

v2.1.4

Compare Source

Patch Changes

  • #​13109 5c0e0ea Thanks @​arnottferels! - Adds support for config.lib, which allows changing the destination of the files:

    export default defineConfig({
	integrations: [partytown({
		config: {
+			lib: '/assets/lib/~partytown/';
		}
	})]
})
withastro/astro (@​astrojs/preact)

v4.1.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

v4.0.11

Compare Source

Patch Changes

v4.0.10

Compare Source

Patch Changes

v4.0.9

Compare Source

Patch Changes

v4.0.8

Compare Source

Patch Changes

v4.0.7

Compare Source

Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

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

v4.0.12

Compare Source

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

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
withastro/astro (@​astrojs/tailwind)

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes
withastro/astro (astro)

v5.9.2

Compare Source

Patch Changes

  • #​13919 423fe60 Thanks @​ematipico! - Fixes a bug where Astro added quotes to the CSP resources.

    Only certain resources require quotes (e.g. 'self' but not https://cdn.example.com), so Astro no longer adds quotes to any resources. You must now provide the quotes yourself for resources such as 'self' when necessary:

    export default defineConfig({
  experimental: {
    csp: {
      styleDirective: {
        resources: [
-          "self",
+          "'self'",
          "https://cdn.example.com"
        ]
      }
    }
  }
})

  • #​13914 76c5480 Thanks @​ematipico! - BREAKING CHANGE to the experimental Content Security Policy feature only

    Removes support for experimental Content Security Policy (CSP) when using the <ClientRouter /> component for view transitions.

    It is no longer possible to enable experimental CSP while using Astro's view transitions. Support was already unstable with the <ClientRouter /> because CSP required making its underlying implementation asynchronous. This caused breaking changes for several users and therefore, this PR removes support completely.

    If you are currently using the component for view transitions, please remove the experimental CSP flag as they cannot be used together.

    import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
-   csp: true
   }
});

    Alternatively, to continue using experimental CSP in your project, you can consider migrating to the browser native View Transition API and remove the <ClientRouter /> from your project. You may be able to achieve similar results if you are not using Astro's enhancements to the native View Transitions and Navigation APIs.

    Support might be reintroduced in future releases. You can follow this experimental feature's development in the CSP RFC.

v5.9.1

Compare Source

Patch Changes

v5.9.0

Compare Source

Minor Changes

  • #​13802 0eafe14 Thanks @​ematipico! - Adds experimental Content Security Policy (CSP) support

    CSP is an important feature to provide fine-grained control over resources that can or cannot be downloaded and executed by a document. In particular, it can help protect against cross-site scripting (XSS) attacks.

    Enabling this feature adds additional security to Astro's handling of processed and bundled scripts and styles by default, and allows you to further configure these, and additional, content types. This new experimental feature has been designed to work in every Astro rendering environment (static pages, dynamic pages and single page applications), while giving you maximum flexibility and with type-safety in mind.

    It is compatible with most of Astro's features such as client islands, and server islands, although Astro's view transitions using the <ClientRouter /> are not yet fully supported. Inline scripts are not supported out of the box, but you can provide your own hashes for external and inline scripts.

    To enable this feature, add the experimental flag in your Astro config:

    // astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    csp: true,
  },
});

    For more information on enabling and using this feature in your project, see the Experimental CSP docs.

    For a complete overview, and to give feedback on this experimental API, see the Content Security Policy RFC.

  • #​13850 1766d22 Thanks @​ascorbic! - Provides a Markdown renderer to content loaders

    When creating a content loader, you will now have access to a renderMarkdown function that allows you to render Markdown content directly within your loaders. It uses the same settings and plugins as the renderer used for Markdown files in Astro, and follows any Markdown settings you have configured in your Astro project.

    This allows you to render Markdown content from various sources, such as a CMS or other data sources, directly in your loaders without needing to preprocess the Markdown content separately.

    import type { Loader } from 'astro/loaders';
import { loadFromCMS } from './cms';

export function myLoader(settings): Loader {
  return {
    name: 'my-loader',
    async load({ renderMarkdown, store }) {
      const entries = await loadFromCMS();

      store.clear();

      for (const entry of entries) {
        // Assume each entry has a 'content' field with markdown content
        store.set(entry.id, {
          id: entry.id,
          data: entry,
          rendered: await renderMarkdown(entry.content),
        });
      }
    },
  };
}

    The return value of renderMarkdown is an object with two properties: html and metadata. These match the rendered property of content entries in content collections, so you can use them to render the content in your components or pages.

v5.8.2

Compare Source

Patch Changes

v5.8.1

Compare Source

Patch Changes

  • #​13037 de2fc9b Thanks @​nanarino! - Fixes rendering of the popover attribute when it has a boolean value

  • #​13851 45ae95a Thanks @​ascorbic! - Allows disabling default styles for responsive images

    This change adds a new image.experimentalDefaultStyles option that allows you to disable the default styles applied to responsive images.

    When using experimental responsive images, Astro applies default styles to ensure the images resize correctly. In most cases this is what you want – and they are applied with low specificity so your own styles override them. However in some cases you may want to disable these default styles entirely. This is particularly useful when using Tailwind 4, because it uses CSS cascade layers to apply styles, making it difficult to override the default styles.

    image.experimentalDefaultStyles is a boolean option that defaults to true, so you can change it in your Astro config file like this:

    export default {
  image: {
    experimentalDefaultStyles: false,
  },
  experimental: {
    responsiveImages: true,
  },
};

  • #​13858 cb1a168 Thanks @​florian-lefebvre! - Fixes the warning shown when client directives are used on Astro components

  • #​12574 da266d0 Thanks @​apatel369! - Allows using server islands in mdx files

  • #​13843 fbcfa68 Thanks @​z1haze! - Export type AstroSession to allow use in explicitly typed safe code.

v5.8.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

v5.7.14

Compare Source

Patch Changes

v5.7.13

Compare Source

Patch Changes

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.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Feb 12, 2025 •
edited
Loading

Deploying blog with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2595718
Status:🚫  Build failed.

View logs

@renovate renovate bot changed the title Update dependency astro to v5.2.6 Update dependency astro to v5.3.0 Feb 13, 2025
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from a3bd592 to bf06edf Compare February 13, 2025 15:30
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from bf06edf to e318a9f Compare February 24, 2025 16:56
@renovate renovate bot changed the title Update dependency astro to v5.3.0 Update astro monorepo Feb 24, 2025
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from a9fcf06 to 0df354f Compare March 4, 2025 15:36
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from 26f285d to c4e7d56 Compare March 17, 2025 17:52
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 292f23c to 0ea3d51 Compare March 21, 2025 16:09
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 229698a to e8846d9 Compare April 1, 2025 11:37
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from fd399da to 0f6fc37 Compare April 8, 2025 12:53
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 6 times, most recently from 8650643 to 0c88f95 Compare April 18, 2025 14:10
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 93f8f69 to 8c3fcf9 Compare April 28, 2025 08:14
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from 40f6192 to 12c2748 Compare April 30, 2025 16:14
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 4697203 to 577c4f9 Compare May 12, 2025 10:43
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from cd955b9 to 61f2fcd Compare May 19, 2025 20:51
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 99fa493 to 3ec57bc Compare May 28, 2025 08:38
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 7a9c66a to 593a1b5 Compare June 4, 2025 11:38
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 47aff1d to d2988d9 Compare June 7, 2025 09:42
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from d2988d9 to 2595718 Compare June 9, 2025 19:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant