Skip to content

[ci] release (beta)#15338

Merged
florian-lefebvre merged 1 commit intonextfrom
changeset-release/next
Jan 30, 2026
Merged

[ci] release (beta)#15338
florian-lefebvre merged 1 commit intonextfrom
changeset-release/next

Conversation

@astrobot-houston
Copy link
Copy Markdown
Contributor

@astrobot-houston astrobot-houston commented Jan 29, 2026 •
edited
Loading

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 next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@6.0.0-beta.6

Major Changes

  • #15332 7c55f80 Thanks @matthewp! - Adds frontmatter parsing support to renderMarkdown in content loaders. When markdown content includes frontmatter, it is now extracted and available in metadata.frontmatter, and excluded from the HTML output. This makes renderMarkdown behave consistently with the glob loader.

    const loader = {
  name: 'my-loader',
  load: async ({ store, renderMarkdown }) => {
    const content = `---
title: My Post
---

# Hello World
`;
    const rendered = await renderMarkdown(content);
    // rendered.metadata.frontmatter is now { title: 'My Post' }
    // rendered.html contains only the content, not the frontmatter
  },
};

Minor Changes

  • #15291 89b6cdd Thanks @florian-lefebvre! - Removes the experimental.fonts flag and replaces it with a new configuration option fonts - (v6 upgrade guidance)

  • #15332 7c55f80 Thanks @matthewp! - Adds a fileURL option to renderMarkdown in content loaders, enabling resolution of relative image paths. When provided, relative image paths in markdown will be resolved relative to the specified file URL and included in metadata.localImagePaths.

    const loader = {
  name: 'my-loader',
  load: async ({ store, renderMarkdown }) => {
    const content = `
# My Post

![Local image](./image.png)
`;
    // Provide a fileURL to resolve relative image paths
    const fileURL = new URL('./posts/my-post.md', import.meta.url);
    const rendered = await renderMarkdown(content, { fileURL });
    // rendered.metadata.localImagePaths now contains the resolved image path
  },
};

  • #15291 89b6cdd Thanks @florian-lefebvre! - Adds a new Fonts API to provide first-party support for adding custom fonts in Astro.

    This feature allows you to use fonts from both your file system and several built-in supported providers (e.g. Google, Fontsource, Bunny) through a unified API. Keep your site performant thanks to sensible defaults and automatic optimizations including preloading and fallback font generation.

    To enable this feature, configure fonts with one or more fonts:

    import { defineConfig, fontProviders } from 'astro/config';

export default defineConfig({
  fonts: [
    {
      provider: fontProviders.fontsource(),
      name: 'Roboto',
      cssVariable: '--font-roboto',
    },
  ],
});

    Import and include the <Font /> component with the required cssVariable property in the head of your page, usually in a dedicated Head.astro component or in a layout component directly:

    ---
// src/layouts/Layout.astro
import { Font } from 'astro:assets';
---

<html>
  <head>
    <Font cssVariable="--font-roboto" preload />
  </head>
  <body>
    <slot />
  </body>
</html>

    In any page rendered with that layout, including the layout component itself, you can now define styles with your font's cssVariable to apply your custom font.

    In the following example, the <h1> heading will have the custom font applied, while the paragraph <p> will not.

    ---
// src/pages/example.astro
import Layout from '../layouts/Layout.astro';
---

<Layout>
  <h1>In a galaxy far, far away...</h1>

  <p>Custom fonts make my headings much cooler!</p>

  <style>
    h1 {
      font-family: var('--font-roboto');
    }
  </style>
</Layout>

    Visit the updated fonts guide to learn more about adding custom fonts to your project.

Patch Changes

  • #15337 7ff7b11 Thanks @ematipico! - Fixes a bug where the development server couldn't serve newly created new pages while the development server is running.

  • #15331 4592be5 Thanks @matthewp! - Fixes an issue where API routes would overwrite public files during build. Public files now correctly take priority over generated routes in both dev and build modes.

  • Updated dependencies [7c55f80]:

    • @astrojs/markdown-remark@7.0.0-beta.3

@astrojs/markdown-remark@7.0.0-beta.3

Minor Changes

  • #15332 7c55f80 Thanks @matthewp! - Exposes the fileURL option in MarkdownProcessorRenderOptions, allowing callers to specify the file URL for resolving relative image paths.

@astrojs/cloudflare@13.0.0-beta.3

Patch Changes

  • #15336 9cce92e Thanks @ascorbic! - Fixes a dev server issue where framework components from linked packages would fail to load with a 504 error.

    This could occur when using client:only or other client directives with components from monorepo packages (linked via file: or workspace protocol). The first request would trigger Vite's dependency optimizer mid-request, causing concurrent client module requests to fail.

  • Updated dependencies []:

    • @astrojs/underscore-redirects@1.0.0

@astrojs/markdoc@1.0.0-beta.6

Patch Changes

  • Updated dependencies [7c55f80]:
    • @astrojs/markdown-remark@7.0.0-beta.3

@astrojs/mdx@5.0.0-beta.3

Patch Changes

  • Updated dependencies [7c55f80]:
    • @astrojs/markdown-remark@7.0.0-beta.3

@github-actions github-actions bot force-pushed the changeset-release/next branch from be68f83 to eb05027 Compare January 29, 2026 15:02
@github-actions github-actions bot added feat: markdown Related to Markdown (scope) pkg: example Related to an example package (scope) pkg: integration Related to any renderer integration (scope) pkg: astro Related to the core `astro` package (scope) labels Jan 29, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 29, 2026

⚠️ Package Trust Level Decreased

Caution

Decreased trust levels may indicate a higher risk of supply chain attacks. Please review these changes carefully.

📦 Package 🔒 Before 🔓 After
eslint-plugin-regexp trusted-with-provenance none
@cloudflare/kv-asset-handler trusted-with-provenance none
@cloudflare/unenv-preset trusted-with-provenance none
workerd trusted-with-provenance none
@sveltejs/vite-plugin-svelte-inspector trusted-with-provenance provenance
@sveltejs/vite-plugin-svelte trusted-with-provenance provenance
jsdoc-type-pratt-parser trusted-with-provenance none
miniflare trusted-with-provenance none
youch provenance none
@cloudflare/workerd-darwin-64 trusted-with-provenance none
@cloudflare/workerd-darwin-arm64 trusted-with-provenance none
@cloudflare/workerd-linux-64 trusted-with-provenance none
@cloudflare/workerd-linux-arm64 trusted-with-provenance none
@cloudflare/workerd-windows-64 trusted-with-provenance none
wrangler trusted-with-provenance none

@github-actions github-actions bot force-pushed the changeset-release/next branch 6 times, most recently from 5a6e145 to de2b096 Compare January 30, 2026 14:08
@github-actions github-actions bot force-pushed the changeset-release/next branch from de2b096 to f016d7f Compare January 30, 2026 14:10
@florian-lefebvre florian-lefebvre merged commit 6f88013 into next Jan 30, 2026
@florian-lefebvre florian-lefebvre deleted the changeset-release/next branch January 30, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@florian-lefebvre florian-lefebvre florian-lefebvre approved these changes

Assignees

No one assigned

Labels

feat: markdown Related to Markdown (scope) pkg: astro Related to the core `astro` package (scope) pkg: example Related to an example package (scope) pkg: integration Related to any renderer integration (scope)

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@astrobot-houston @florian-lefebvre