chore(release): v1.5.0

Also widens core's optional katex peer to ^0.16.0 || ^0.17.0 — the
old ^0.16.0 range excluded the 0.17 line the repo itself tests
against, giving npm consumers on katex 0.17 spurious ERESOLVE
conflicts — and syncs the READMEs' Mantine peer tables to ^9.0.0.

Author: AIEPhoenix

README.md

@@ -83,13 +83,13 @@ pnpm add @ai-react-markdown/mantine @ai-react-markdown/core \
 
 ### Peer Dependencies
 
-| Peer                      | Required by                                    | Version    |
-| ------------------------- | ---------------------------------------------- | ---------- |
-| `react` / `react-dom`     | both packages                                  | `>=19.0.0` |
-| `katex`                   | `core` (optional — only if you import its CSS) | `^0.16.0`  |
-| `@mantine/core`           | `mantine`                                      | `^8.3.17`  |
-| `@mantine/code-highlight` | `mantine`                                      | `^8.3.17`  |
-| `highlight.js`            | `mantine`                                      | `^11.11.1` |
+| Peer                      | Required by                                    | Version                |
+| ------------------------- | ---------------------------------------------- | ---------------------- |
+| `react` / `react-dom`     | both packages                                  | `>=19.0.0`             |
+| `katex`                   | `core` (optional — only if you import its CSS) | `^0.16.0 \|\| ^0.17.0` |
+| `@mantine/core`           | `mantine`                                      | `^9.0.0`               |
+| `@mantine/code-highlight` | `mantine`                                      | `^9.0.0`               |
+| `highlight.js`            | `mantine`                                      | `^11.11.1`             |
 
 > `katex` is an **optional peer**. It ships transitively via `rehype-katex`, so hoisted installers (npm, yarn classic, default pnpm) resolve `'katex/dist/katex.min.css'` automatically. Strict-isolation installers (yarn PnP, `pnpm --node-linker=isolated`) must install it explicitly. Skip this only if you never render math.
 
@@ -672,7 +672,7 @@ Issues and pull requests are welcome. For non-trivial changes, please open an is
 
 Reporting a bug helps most when it includes:
 
-- The package and version (`@ai-react-markdown/core@1.4.9` …)
+- The package and version (`@ai-react-markdown/core@1.5.0` …)
 - The relevant `<AIMarkdown>` / `<MantineAIMarkdown>` props
 - A minimal markdown sample that reproduces the issue
 - For streaming-related bugs: the chunk sequence (one string per chunk)

docs/release-highlights.md

@@ -6,6 +6,15 @@ A distilled, human-readable summary of what's notable in each version — extrac
 
 ---
 
+## 1.5.x — Mantine 9
+
+### 1.5.0 — `@ai-react-markdown/mantine` moves to Mantine 9
+
+- `@ai-react-markdown/mantine` now requires `@mantine/core` and `@mantine/code-highlight` `^9.0.0` as peers (tested against 9.4.1). No API changes on our side — the package's surface survives every Mantine 9 breaking change untouched. Consumers inherit Mantine 9's defaults: `md` (8px) default radius, solid light-variant colors (Mantine's `v8CssVariablesResolver` restores the 8.x look), and a React 19.2 floor.
+- If you install `@mantine/hooks` yourself, note that `@mantine/core@9` pins its hooks peer to the exact matching version — keep the three `@mantine/*` packages on one version.
+- Core is unchanged in behavior. One internal type adaptation for `@types/hast` ≥3.0.5: the aggregated footnote footer's `<li>` numbering is now stored as a string in hast (`value: "3"` instead of `value: 3`) — the rendered DOM is byte-identical.
+- Core's optional `katex` peer widens to `^0.16.0 || ^0.17.0`. The range previously excluded 0.17 (a `^0.16.0` range does not match 0.17 under 0.x semver), so npm users on katex 0.17 hit spurious `ERESOLVE` conflicts — even though the library is continuously tested against 0.17.
+
 ## 1.4.x — Customization surface hardening
 
 The 1.4 line opened up the customization surface (URL sanitization, document namespacing, design tokens) and put guardrails around it so consumers can extend safely.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-react-markdown",
-  "version": "1.4.9",
+  "version": "1.5.0",
   "private": true,
   "type": "module",
   "description": "A React component for rendering AI-generated Markdown with LaTeX math, GFM, syntax highlighting and more.",

packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-react-markdown/core",
-  "version": "1.4.9",
+  "version": "1.5.0",
   "description": "Core rendering engine for ai-react-markdown — LaTeX preprocessing, plugin pipeline, and React components.",
   "publishConfig": {
     "access": "public"
@@ -61,7 +61,7 @@
   "peerDependencies": {
     "react": ">=19.0.0",
     "react-dom": ">=19.0.0",
-    "katex": "^0.16.0"
+    "katex": "^0.16.0 || ^0.17.0"
   },
   "peerDependenciesMeta": {
     "katex": {

packages/mantine/README.md

@@ -36,9 +36,9 @@ yarn add @ai-react-markdown/mantine @ai-react-markdown/core
 {
   "react": ">=19",
   "react-dom": ">=19",
-  "@ai-react-markdown/core": "^1.4.9",
-  "@mantine/core": "^8.3.17",
-  "@mantine/code-highlight": "^8.3.17",
+  "@ai-react-markdown/core": "^1.5.0",
+  "@mantine/core": "^9.0.0",
+  "@mantine/code-highlight": "^9.0.0",
   "highlight.js": "^11.11.1"
 }
 ```

packages/mantine/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-react-markdown/mantine",
-  "version": "1.4.9",
+  "version": "1.5.0",
   "description": "Mantine UI integration for ai-react-markdown — themed typography, syntax highlighting via @mantine/code-highlight, Mermaid diagrams, and automatic color scheme detection.",
   "publishConfig": {
     "access": "public"
@@ -56,7 +56,7 @@
     "typecheck": "tsc --noEmit -p tsconfig.json"
   },
   "peerDependencies": {
-    "@ai-react-markdown/core": "^1.4.9",
+    "@ai-react-markdown/core": "^1.5.0",
     "@mantine/code-highlight": "^9.0.0",
     "@mantine/core": "^9.0.0",
     "highlight.js": "^11.11.1",