[ci] release (alpha)

[astrobot-houston]

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

@astrojs/markdoc@1.0.0-alpha.1

Minor Changes

• #15097 be1b9bf Thanks @matthewp! - Updates internal image processing to be compatible with Astro 6. This change is internal-only and does not affect the public API.

  The integration now uses Astro's new emitImageMetadata() function instead of the removed emitESMImage() function for processing images referenced in Markdoc content during build time. This ensures continued compatibility with Astro's asset processing pipeline while maintaining the same behavior for users.

astro@6.0.0-alpha.5

Patch Changes

• #15064 caf5621 Thanks @ascorbic! - Fixes a bug that caused incorrect warnings of duplicate entries to be logged by the glob loader when editing a file

• #15093 8d5f783 Thanks @matthewp! - Reduces build memory by filtering routes per environment so each only builds the pages it needs

• #15073 2a39c32 Thanks @ascorbic! - Don't log an error when there is no content config

• #15112 5751d2b Thanks @HiDeoo! - Fixes a Windows-specific build issue when importing an Astro component with a <script> tag using an import alias.

@astrojs/cloudflare@13.0.0-alpha.4

Patch Changes

• #15079 4463a55 Thanks @ascorbic! - Fixes auto-provisioning of default bindings (SESSION KV, IMAGES, and ASSETS). Default bindings are now correctly applied whether or not you have a wrangler.json file.
  Previously, these bindings were only added when no wrangler config file existed. Now they are added in both cases, unless you've already defined them yourself.

• #15075 ee2c260 Thanks @matthewp! - Adds deprecation errors for Astro.locals.runtime properties to help migrate from Astro v5 to v6

  When accessing the removed Astro.locals.runtime properties on Cloudflare, developers now receive clear error messages explaining the migration path:

  • Astro.locals.runtime.env → Use import { env } from "cloudflare:workers"
  • Astro.locals.runtime.cf → Use Astro.request.cf
  • Astro.locals.runtime.caches → Use the global caches object
  • Astro.locals.runtime.ctx → Use Astro.locals.cfContext

• Updated dependencies []:

  • @astrojs/underscore-redirects@1.0.0

[github-actions]

⚠️ 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
@cloudflare/unenv-preset	trusted-with-provenance	none
workerd	trusted-with-provenance	none
undici	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