Skip to content
verdict:

Astro 7.0.0-beta.3

preview

Release notes

note: no summary for this older release

We summarize recent releases. The original release notes for this version are below.

release-notesgithub.com/withastro/astro · 145 lines
  1. ### Major Changes
  3. - [#17010](https://github.com/withastro/astro/pull/17010) [`0606073`](https://github.com/withastro/astro/commit/0606073794ddda42cac1f3e1ca56bbfc7cb178eb) Thanks [@ocavue](https://github.com/ocavue)! - Removes the `astro db`, `astro login`, `astro logout`, `astro link`, and `astro init` CLI commands.
  5. The `@astrojs/db` package is now deprecated. We recommend using a database client (Drizzle, Kysely, etc.) directly instead.
  7. - [#16877](https://github.com/withastro/astro/pull/16877) [`3b7d76e`](https://github.com/withastro/astro/commit/3b7d76e6decff6b236d1b30d901b4fa339edb960) Thanks [@matthewp](https://github.com/matthewp)! - Enables advanced routing by default.
  9. The advanced routing feature introduced behind a flag in [v6.3.0](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#630) is no longer experimental and is now enabled by default.
  11. This gives full control over how requests flow through your application, with first-class support for frameworks like Hono.
  13. Advanced routing now uses `src/fetch.ts` as default entrypoint instead of `src/app.ts`.
  15. If you were previously using this feature without a custom entrypoint, please configure `fetchFile` or rename your entrypoint to `src/fetch.ts`, and then remove the experimental flag from your Astro config:
  17. ```diff
  18. import { defineConfig } from 'astro/config';
  20. export default defineConfig({
  21. experimental {
  22. - advancedRouting: true,
  23. },
  24. + fetchFile: 'app.ts' // optional, you only need this if you cannot rename your entrypoint.
  25. });
  26. ```
  28. `fetchFile` is now a top-level config option instead of being nested under `experimental.advancedRouting`. If you were using a custom entrypoint, please update your Astro config to move its configuration:
  30. ```diff
  31. // astro.config.mjs
  32. export default defineConfig({
  33. - experimental: {
  34. - advancedRouting: {
  35. - fetchFile: 'my-custom-entrypoint.ts',
  36. - },
  37. - },
  38. + fetchFile: 'my-custom-entrypoint.ts',
  39. })
  40. ```
  42. You can also set `fetchFile: null` to disable the entrypoint if you are using `src/fetch.ts` for another purpose, or don’t need advanced routing features.
  44. If you have been waiting for stabilization before using advanced routing, you can now do so.
  46. Please see [the advanced routing guide in docs](https://docs.astro.build/en/guides/routing/#advanced-routing) for more about this feature.
  48. ### Minor Changes
  50. - [#16998](https://github.com/withastro/astro/pull/16998) [`57dcc31`](https://github.com/withastro/astro/commit/57dcc31bb78575a89304ab5310f2f5911a83f3af) Thanks [@matthewp](https://github.com/matthewp)! - Exposes `getFetchState()` from `astro/hono` as a public API
  52. The `getFetchState()` function retrieves or lazily creates a `FetchState` from a Hono context object. This allows third-party packages to build Hono middleware that interacts with Astro's per-request state, giving the `astro/hono` API the same extensibility as `astro/fetch`.
  54. ```ts
  55. import { Hono } from 'hono';
  56. import { getFetchState, pages } from 'astro/hono';
  58. const app = new Hono();
  60. app.use(async (context, next) => {
  61. const state = getFetchState(context);
  62. state.locals.message = 'Hello from custom middleware';
  63. await next();
  64. });
  66. app.use(pages());
  68. export default app;
  69. ```
  71. - [#16996](https://github.com/withastro/astro/pull/16996) [`300641e`](https://github.com/withastro/astro/commit/300641e588ac74968197bd87e0a97f71d132946e) Thanks [@florian-lefebvre](https://github.com/florian-lefebvre)! - Adds a `subset` field to the `FontData` type exposed via `fontData` from `astro:assets`. When using multiple font subsets (e.g., `subsets: ["latin", "korean"]`), each font data entry now includes the subset name, making it possible to distinguish between font entries for different subsets that share the same weight and style.
  73. - [#16745](https://github.com/withastro/astro/pull/16745) [`f864a80`](https://github.com/withastro/astro/commit/f864a808c5dd83e19be66bb5227edffbe506a697) Thanks [@ematipico](https://github.com/ematipico)! - The custom logger feature introduced behind a flag in [v6.2.0](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#620) is no longer experimental and is available for general use.
  75. This feature provides better control over Astro's logging infrastructure by allowing you to replace the default console output with custom logging implementations (e.g., structured JSON). This is particularly useful for on-demand rendering when connecting to log aggregation services such as Kibana, Logstash, CloudWatch, Grafana, or Loki.
  77. Astro provides three built-in log handlers (`json`, `node`, and `console`), and you can also create your own.
  79. #### JSON logging
  81. ```js
  82. import { defineConfig, logHandlers } from 'astro/config';
  84. export default defineConfig({
  85. logger: logHandlers.json({
  86. pretty: true,
  87. level: 'warn',
  88. }),
  89. });
  90. ```
  92. #### Custom logger
  94. ```js
  95. import { defineConfig } from 'astro/config';
  97. export default defineConfig({
  98. logger: {
  99. entrypoint: '@org/custom-logger',
  100. },
  101. });
  102. ```
  104. Additionally, `context.logger` is now always available in API routes and middleware, even without a custom logger configured.
  106. If you were previously using this feature, please remove the experimental flag from your Astro config:
  108. ```diff
  109. import { defineConfig } from 'astro/config';
  111. export default defineConfig({
  112. - experimental: {
  113. - logger: {
  114. - entrypoint: '@org/custom-logger',
  115. - },
  116. - },
  117. + logger: {
  118. + entrypoint: '@org/custom-logger',
  119. + },
  120. });
  121. ```
  123. If you have been waiting for stabilization before using custom loggers, you can now do so.
  125. Please see the [Logger docs](https://docs.astro.build/en/reference/configuration-reference/#logger) for more about this feature.
  127. - [#16981](https://github.com/withastro/astro/pull/16981) [`0d6d644`](https://github.com/withastro/astro/commit/0d6d64433fa31762b6fd593da902f63f3204e02a) Thanks [@ematipico](https://github.com/ematipico)! - Removes the setting `experimental.queuedRendering`. The new rendering engine is now stable and replaces the old one.
  129. As part of the stabilization, the queued rendering has been improved, and some features have been removed:
  131. - The construction of the queue has been removed, instead now Astro uses a streaming approach where components are rendered and flushed as they are encountered.
  132. - The node polling feature has been removed because it doesn't yield concrete savings.
  133. - The content cache has been descoped, and how only tag names are cached.
  134. If you were previously using this experimental feature, you must remove this experimental flag from your configuration as it no longer exists:
  136. ```diff
  137. // astro.config.mjs
  138. import { defineConfig } from "astro/config";
  140. export default defineConfig({
  141. experimental: {
  142. - queuedRendering: {}
  143. }
  144. });
  145. ```

view on githubimported 2026-09-28 via npm