[ci] release (#13086)astro@5.2.0@astrojs/tailwind@6.0.0@astrojs/mdx@4.0.8@astrojs/markdown-remark@6.1.0@astrojs/markdoc@0.12.8@astrojs/internal-helpers@0.5.0

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

9 files changed, 0 insertions, 125 deletions

diff --git a/.changeset/blue-jokes-eat.md b/.changeset/blue-jokes-eat.md
deleted file mode 100644
index a5a584ce1..000000000
--- a/.changeset/blue-jokes-eat.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@astrojs/internal-helpers': minor
----
-
-Adds `collapseDuplicateTrailingSlashes` function
diff --git a/.changeset/blue-spies-shave.md b/.changeset/blue-spies-shave.md
deleted file mode 100644
index 562de6a46..000000000
--- a/.changeset/blue-spies-shave.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'astro': minor
----
-
-Redirects trailing slashes for on-demand pages
-
-When the `trailingSlash` option is set to `always` or `never`, on-demand rendered pages will now redirect to the correct URL when the trailing slash doesn't match the configuration option. This was previously the case for static pages, but now works for on-demand pages as well.
-
-Now, it doesn't matter whether your visitor navigates to `/about/`, `/about`, or even `/about///`. In production, they'll always end up on the correct page. For GET requests, the redirect will be a 301 (permanent) redirect, and for all other request methods, it will be a 308 (permanent, and preserve the request method) redirect.
-
-In development, you'll see a helpful 404 page to alert you of a trailing slash mismatch so you can troubleshoot routes.
diff --git a/.changeset/curvy-penguins-act.md b/.changeset/curvy-penguins-act.md
deleted file mode 100644
index e36bbfbf0..000000000
--- a/.changeset/curvy-penguins-act.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astrojs/tailwind': major
----
-
-Deprecates the integration
-
-Tailwind CSS now offers a Vite plugin which is the preferred way to use Tailwind 4 in Astro. Please uninstall `@astrojs/tailwind` and follow the [Tailwind documentation for manual installation](https://tailwindcss.com/docs/installation/framework-guides/astro).
-
-This updated major version is only provided as a convenience for existing projects until they are able to migrate to the new plugin. It offers no additional functionality and is no longer recommended, but may continue to be used in your projects until it is removed entirely.
diff --git a/.changeset/four-chairs-exercise.md b/.changeset/four-chairs-exercise.md
deleted file mode 100644
index 906c85d34..000000000
--- a/.changeset/four-chairs-exercise.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'astro': patch
----
-
-Updates `astro add tailwind` to add the `@tailwindcss/vite` plugin instead of the `@astrojs/tailwind` integration
diff --git a/.changeset/lazy-pandas-love.md b/.changeset/lazy-pandas-love.md
deleted file mode 100644
index 63e4ee2cd..000000000
--- a/.changeset/lazy-pandas-love.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-'@astrojs/markdown-remark': minor
----
-
-Adds support for TOML frontmatter in `.md` and `.mdx` files
-
-Astro 5.2 automatically identifies the format of your Markdown and MDX frontmatter based on the delimiter used.  With `+++` as a delimiter (instead of the `---` YAML code fence), your frontmatter will automatically be recognized and parsed as [TOML](https://toml.io). 
-
-This is useful for adding existing content files with TOML frontmatter to your project from another framework such as Hugo.
-
-TOML frontmatter can also be used with [content collections](https://docs.astro.build/guides/content-collections/), and files with different frontmatter languages can live together in the same project.
-
-No configuration is required to use TOML frontmatter in your content files. Your delimiter will indicate your chosen frontmatter language:
-
-```md
-+++
-date = 2025-01-30
-title = 'Use TOML frontmatter in Astro!'
-[author]
-name = 'Colin Bate'
-+++
-
-# Support for TOML frontmatter is here!
-```
diff --git a/.changeset/light-pants-smoke.md b/.changeset/light-pants-smoke.md
deleted file mode 100644
index 6a7f4a15b..000000000
--- a/.changeset/light-pants-smoke.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-'astro': minor
----
-
-Adds support for redirecting to external sites with the [`redirects`](https://docs.astro.build/en/reference/configuration-reference/#redirects) configuration option.
-
-Now, you can redirect routes either internally to another path or externally by providing a URL beginning with `http` or `https`:
-
-```js 
-// astro.config.mjs
-import {defineConfig} from "astro/config"
-
-export default defineConfig({
-  redirects: {
-    "/blog": "https://example.com/blog",
-    "/news": {
-      status: 302,
-      destination: "https://example.com/news" 
-    }
-  }
-})
-```
diff --git a/.changeset/many-fans-battle.md b/.changeset/many-fans-battle.md
deleted file mode 100644
index 8240531d0..000000000
--- a/.changeset/many-fans-battle.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'astro': patch
----
-
-Returns a more helpful 404 page in dev if there is a trailing slash mismatch between the route requested and the `trailingSlash` configuration
diff --git a/.changeset/sharp-clouds-begin.md b/.changeset/sharp-clouds-begin.md
deleted file mode 100644
index 12b857a5a..000000000
--- a/.changeset/sharp-clouds-begin.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'astro': patch
----
-
-Added additional generated typings for the content layer
diff --git a/.changeset/stupid-glasses-switch.md b/.changeset/stupid-glasses-switch.md
deleted file mode 100644
index d33db244e..000000000
--- a/.changeset/stupid-glasses-switch.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-'astro': minor
----
-
-Adds a new experimental virtual module `astro:config` that exposes a type-safe subset of your `astro.config.mjs` configuration
-
-The virtual module exposes two sub-paths for controlled access to your configuration:
-- `astro:config/client`: exposes config information that is safe to expose to the client.
-- `astro:config/server`: exposes additional information that is safe to expose to the server, such as file/dir paths.
-
-To enable this new virtual module, add the `experimental.serializeManifest` feature flag to your Astro config:
-
-```js
-// astro.config.mjs
-import {defineConfig} from "astro/config"
-export default defineConfig({
-  experimental: {
-    serializeManifest: true
-  }
-})
-```
-
-Then, you can access the module in any file inside your project to import and use values from your Astro config:
-
-```js
-// src/utils.js
-import { trailingSlash } from "astro:config/client";
-
-function addForwardSlash(path) {
-  if (trailingSlash === "always") {
-    return path.endsWith("/") ? path : path + "/"
-  } else {
-    return path
-  }
-}
-
-```
-
-For a complete overview, and to give feedback on this experimental API, see the [Serialized Manifest RFC](https://github.com/withastro/roadmap/blob/feat/serialised-config/proposals/0051-serialized-manifest.md).