Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ci] release #13318

Merged
merged 1 commit into from
Feb 27, 2025
Merged

[ci] release #13318

merged 1 commit into from
Feb 27, 2025

Conversation

astrobot-houston
Copy link
Contributor

@astrobot-houston astrobot-houston commented Feb 26, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.4.0

Minor Changes

  • #12052 5be12b2 Thanks @Fryuni! - Exposes extra APIs for scripting and testing.

    Config helpers

    Two new helper functions exported from astro/config:

    • mergeConfig() allows users to merge partially defined Astro configurations on top of a base config while following the merge rules of updateConfig() available for integrations.
    • validateConfig() allows users to validate that a given value is a valid Astro configuration and fills in default values as necessary.

    These helpers are particularly useful for integration authors and for developers writing scripts that need to manipulate Astro configurations programmatically.

    Programmatic build

    The build API now receives a second optional BuildOptions argument where users can specify:

    • devOutput (default false): output a development-based build similar to code transformed in astro dev.
    • teardownCompiler (default true): teardown the compiler WASM instance after build.

    These options provide more control when running Astro builds programmatically, especially for testing scenarios or custom build pipelines.

  • #13278 4a43c4b Thanks @ematipico! - Adds a new configuration option server.allowedHosts and CLI option --allowed-hosts.

    Now you can specify the hostnames that the dev and preview servers are allowed to respond to. This is useful for allowing additional subdomains, or running the dev server in a web container.

    allowedHosts checks the Host header on HTTP requests from browsers and if it doesn't match, it will reject the request to prevent CSRF and XSS attacks.

    astro dev --allowed-hosts=foo.bar.example.com,bar.example.com
    astro preview --allowed-hosts=foo.bar.example.com,bar.example.com
    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      server: {
        allowedHosts: ['foo.bar.example.com', 'bar.example.com'],
      },
    });

    This feature is the same as Vite's server.allowHosts configuration.

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

    Previously, Astro only allowed local images to be optimized when included using ![]() syntax in plain Markdown files. 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 HTML <img> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

  • #13256 509fa67 Thanks @p0lyw0lf! - Adds experimental responsive image support in Markdown

    Previously, the experimental.responsiveImages feature could only provide responsive images when using the <Image /> and <Picture /> components.

    Now, images written with the ![]() Markdown syntax in Markdown and MDX files will generate responsive images by default when using this experimental feature.

    To try this experimental feature, set experimental.responsiveImages to true in your astro.config.mjs file:

    {
       experimental: {
          responsiveImages: true,
       },
    }

    Learn more about using this feature in the experimental responsive images feature reference.

    For a complete overview, and to give feedback on this experimental API, see the Responsive Images RFC.

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • #13313 9e7c71d Thanks @martrapp! - Fixes an issue where a form field named "attributes" shadows the form.attributes property.

  • #12052 5be12b2 Thanks @Fryuni! - Fixes incorrect config update when calling updateConfig from astro:build:setup hook.

    The function previously called a custom update config function made for merging an Astro config. Now it calls the appropriate mergeConfig() utility exported by Vite that updates functional options correctly.

  • #13303 5f72a58 Thanks @ematipico! - Fixes an issue where the dev server was applying second decoding of the URL of the incoming request, causing issues for certain URLs.

  • Updated dependencies [1e11f5e, 1e11f5e]:

    • @astrojs/internal-helpers@0.6.0
    • @astrojs/markdown-remark@6.2.0

@astrojs/mdx@4.1.0

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

  • Updated dependencies [1e11f5e]:
    • @astrojs/markdown-remark@6.2.0

@astrojs/vercel@8.1.0

Minor Changes

  • #13211 7ea0aba Thanks @slawekkolodziej! - Adds support for regular expressions in ISR exclude list

    Previously, excluding a page from ISR required explicitly listing it in isr.exclude. As websites grew larger, maintaining this list became increasingly difficult, especially for multiple API routes and pages that needed server-side rendering.

    To address this, ISR exclusions now support regular expressions, allowing for more flexible and scalable configurations.

    // astro.config.mjs
    import vercel from '@astrojs/vercel/serverless';
    
    export default defineConfig({
      output: 'server',
      adapter: vercel({
        isr: {
          exclude: [
            '/preview', // Excludes a specific route (e.g., pages/preview.astro)
            '/auth/[page]', // Excludes a dynamic route (e.g., pages/auth/[page].astro)
            /^\/api\/.+/, // Excludes all routes starting with /api/
          ],
        },
      }),
    });

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • Updated dependencies [1e11f5e]:

    • @astrojs/internal-helpers@0.6.0

@astrojs/internal-helpers@0.6.0

Minor Changes

  • #13254 1e11f5e Thanks @p0lyw0lf! - Adds remote URL filtering utilities

    This adds logic to filter remote URLs so that it can be used by both astro and @astrojs/markdown-remark.

@astrojs/markdown-remark@6.2.0

Minor Changes

  • #13254 1e11f5e Thanks @p0lyw0lf! - Adds remote image optimization in Markdown

    Previously, an internal remark plugin only looked for images in ![]() syntax that referred to a relative file path. This meant that only local images stored in src/ were passed through to an internal rehype plugin that would transform them for later processing by Astro's image service.

    Now, the plugins recognize and transform both local and remote images using this syntax. Only authorized remote images specified in your config are transformed; remote images from other sources will not be processed.

    While not configurable at this time, this process outputs two separate metadata fields (localImagePaths and remoteImagePaths) which allow for the possibility of controlling the behavior of each type of image separately in the future.

Patch Changes

  • Updated dependencies [1e11f5e]:
    • @astrojs/internal-helpers@0.6.0

@astrojs/db@0.14.7

Patch Changes

  • #13314 797a948 Thanks @jlebras! - Expose ilike function from drizzle-orm

  • Updated dependencies []:

    • @astrojs/studio@0.1.4

@astrojs/cloudflare@12.2.3

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • Updated dependencies [1e11f5e]:

    • @astrojs/internal-helpers@0.6.0
    • @astrojs/underscore-redirects@0.6.0

@astrojs/markdoc@0.12.10

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • Updated dependencies [1e11f5e, 1e11f5e]:

    • @astrojs/internal-helpers@0.6.0
    • @astrojs/markdown-remark@6.2.0

@astrojs/netlify@6.2.2

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • Updated dependencies [1e11f5e]:

    • @astrojs/internal-helpers@0.6.0
    • @astrojs/underscore-redirects@0.6.0

@astrojs/node@9.1.2

Patch Changes

  • Updated dependencies [1e11f5e]:
    • @astrojs/internal-helpers@0.6.0

@astrojs/preact@4.0.5

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

@astrojs/react@4.2.1

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

@astrojs/solid-js@5.0.5

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

@astrojs/svelte@7.0.5

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

@github-actions github-actions bot force-pushed the changeset-release/main branch 14 times, most recently from 59082a4 to 4c4cb54 Compare February 27, 2025 10:45
@github-actions github-actions bot force-pushed the changeset-release/main branch from 4c4cb54 to 8eccac2 Compare February 27, 2025 10:46
@ematipico ematipico merged commit 9aa5ac1 into main Feb 27, 2025
@ematipico ematipico deleted the changeset-release/main branch February 27, 2025 13:26
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.

2 participants