[ci] release (beta)

[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

astro@4.0.0-beta.2

Major Changes

• #9225 c421a3d17 Thanks @natemoo-re! - Removes the opt-in handleForms property for <ViewTransitions />. Form submissions are now handled by default and can be disabled by setting data-astro-reload on relevant <form /> elements.

• #9199 49aa215a0 Thanks @lilnasy! - This change only affects maintainers of third-party adapters. In the Integration API, the app.render() method of the App class has been simplified.

  Instead of two optional arguments, it now takes a single optional argument that is an object with two optional properties: routeData and locals.

   app.render(request)
  
  - app.render(request, routeData)
  + app.render(request, { routeData })
  
  - app.render(request, routeData, locals)
  + app.render(request, { routeData, locals })
  
  - app.render(request, undefined, locals)
  + app.render(request, { locals })

  The current signature is deprecated but will continue to function until next major version.

• #9212 c0383ea0c Thanks @alexanderniebuhr! - Removes deprecated app.match() option, matchNotFound

Minor Changes

• #9115 3b77889b4 Thanks @natemoo-re! - Adds the astro preferences command to manage user preferences. User preferences are specific to individual Astro users, unlike the astro.config.mjs file which changes behavior for everyone working on a project.

  User preferences are scoped to the current project by default, stored in a local .astro/settings.json file. Using the --global flag, user preferences can also be applied to every Astro project on the current machine. Global user preferences are stored in an operating system-specific location.

  # Disable the dev overlay for the current user in the current project
  npm run astro preferences disable devOverlay
  # Disable the dev overlay for the current user in all Astro projects on this machine
  npm run astro preferences --global disable devOverlay
  
  # Check if the dev overlay is enabled for the current user
  npm run astro preferences list devOverlay

• #9129 8bfc20511 Thanks @FredKSchott! - Update error log formatting

Patch Changes

• #9222 279e3c1b3 Thanks @matthewp! - Ensure the dev-overlay-window is anchored to the bottom

• #9218 f4401c8c1 Thanks @matthewp! - Improve high contrast mode with the Dev Overlay

• #9227 4b8a42406 Thanks @matthewp! - Ensure overlay x-ray z-index is higher than the island

• #9214 4fe523b00 Thanks @Princesseuh! - Fixes a number of small user experience bugs with the dev overlay

@astrojs/node@7.0.0-beta.1

Major Changes

• #9199 49aa215a0 Thanks @lilnasy! - The internals of the integration have been updated to support Astro 4.0. Make sure to upgrade your Astro version as Astro 3.0 is no longer supported.

@astrojs/vercel@6.0.0-beta.1

Major Changes

• #9199 49aa215a0 Thanks @lilnasy! - The internals of the integration have been updated to support Astro 4.0. Make sure to upgrade your Astro version as Astro 3.0 is no longer supported.