From 68284978af8b1d0e5c21cb1bcd6594668a192182 Mon Sep 17 00:00:00 2001
From: Yan Wang <ywang@talend.com>
Date: Tue, 24 Dec 2024 18:28:43 +0800
Subject: [PATCH] changeset

---
 .changeset/breezy-ways-care.md | 35 ++++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 .changeset/breezy-ways-care.md

diff --git a/.changeset/breezy-ways-care.md b/.changeset/breezy-ways-care.md
new file mode 100644
index 0000000000..d26d87d91b
--- /dev/null
+++ b/.changeset/breezy-ways-care.md
@@ -0,0 +1,35 @@
+---
+'@talend/react-cmf-router': major
+'@talend/react-cmf': major
+---
+
+BREAKING CHANGE: Upgraded path-to-regexp from 3.x to 8.x
+
+This upgrade was necessary to resolve security vulnerabilities. The new version introduces two breaking changes that require updates to your application:
+
+1. Optional Path Parameter Syntax Change
+- Old syntax: `/resources/:id?`
+- New syntax: `/resources{/id}`
+
+This change is required because in path-to-regexp 8.x, the `?` character is reserved for query parameters and will throw a parsing error when used at the end of a path.
+
+2. Root Path Matching Behavior Change
+- In v3.x, root path `/` would match any path starting with `/`
+- In v8.x, root path `/` only matches exactly `/`
+- To match both root and child paths, use the wildcard pattern `/{*path}`
+
+Example migration:
+```javascript
+// Before
+const routes = {
+    '/': rootSaga,
+    '/resources/:id?': resourceSaga
+};
+
+// After
+const routes = {
+    '/{*path}': rootSaga,  // if you want to match all routes
+    '/resources{/id}': resourceSaga
+};
+```
+For more details about path matching and troubleshooting, see [path-to-regexp documentation](https://github.com/pillarjs/path-to-regexp#errors).
\ No newline at end of file