chore: prepare release

[build-travis-ci]

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 master, this PR will be updated.

Releases

@talend/[email protected]

Major Changes

• 816bb91: 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:

  // 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.

@talend/[email protected]

Major Changes

• 816bb91: 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:

  // 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.

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]

@talend/[email protected]

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]

@talend/[email protected]

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]

@talend/[email protected]

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]

@talend/[email protected]

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]

@talend/[email protected]

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]
  • @talend/[email protected]
  • @talend/[email protected]

@talend/[email protected]

Patch Changes

• Updated dependencies [816bb91]
  • @talend/[email protected]
  • @talend/[email protected]
  • @talend/[email protected]

[github-actions]

Storybook for this PR deployed on this github page

[github-actions]

Title	Lines	Statements	Branches	Functions
assets-api		28.4% (25/88)	30.76% (16/52)	21.42% (3/14)
cmf		89.36% (1243/1391)	80.93% (607/750)	89.51% (350/391)
cmf-cqrs		87.43% (160/183)	70.23% (59/84)	84.21% (48/57)
cmf-router		69.23% (135/195)	55.71% (78/140)	56.81% (25/44)
components		90.8% (5527/6087)	81.84% (3206/3917)	88.14% (1390/1577)
containers		83.59% (1391/1664)	74.3% (694/934)	75% (327/436)
dataviz		85.44% (323/378)	66.66% (160/240)	75.79% (119/157)
design-system		66.49% (1016/1528)	50.93% (544/1068)	53.94% (219/406)
faceted-search		85.08% (639/751)	78.63% (287/365)	81.88% (226/276)
flow-designer		70.07% (651/929)	66.72% (355/532)	70.92% (200/282)
forms		85.81% (1640/1911)	75.77% (929/1226)	84.24% (460/546)
http		100% (85/85)	98.07% (51/52)	100% (34/34)
sagas		92.3% (24/26)	66.66% (4/6)	50% (2/4)
stepper		81.52% (150/184)	59.34% (54/91)	80.85% (38/47)
utils		100% (73/73)	90.9% (10/11)	100% (24/24)