Merge pull request #277 from eccenca/feature/supportReactFlow-v9-v10-v12-CMEM-4900-CMEM-6506

Support React Flow v12 (CMEM-4900 & CMEM-6506)

Author: andreas-schultz

CHANGELOG.md

@@ -6,6 +6,8 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 
 ## [Unreleased]
 
+This is a major release, and it might be not compatible with your current usage of our library. Please read about the necessary changes in the section about how to migrate.
+
 ### Added
 
 -   Extended existing height and readOnly props from `CodeEditorProps` to `AutoSuggestionProps` & `ExtendedCodeEditorProps` to be configurable from `<CodeAutocompleteField />`
@@ -58,6 +60,11 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 
 ### Changed
 
+-   `eslint` libraries were upgraded to v9, so `node` v18.18 or higher is required
+-   react flow integration by renaming their resources from `legacy` and `next` to more precise `v9` and `v10`:
+    -   `HandleProps`: renamed to `HandleV9Props`
+    -   `HandleNextProps`: renamed to `HandleV10Props`
+    -   if provided then the `flowVersion` property do not accept `legacy` and `next` as values anymore, use `v9` and `v10`
 -   some more interfaces are exposed:
     -   `IntentBlueprint`: BlueprintJS intent types, also available by `DefinitionsBlueprint`
     -   `TableDataContainerProps`, `TableSimpleContainerProps`, `TableHeadProps`, `TableBodyProps`, `TableExpandedRowProps`, `TableHeaderProps` and `DataTableRenderProps` as interfaces for diverse table components
@@ -80,6 +87,18 @@ Old bundlers like webpack4 do not support the `exports` field from `package.json
 
 If you use Jest then you can use the same aliases for the `moduleNameMapper` config, if necessary.
 
+### Deprecated
+
+-   `HandleV9Props` and `HandleV10Props` export will be removed, use only `HandleDefaultProps`
+-   `<NodeContent />`
+    -   `businessDate`: will be removed because it is already not used
+-   `<ReactFlow />`: use `<ReactFlowExtended />`
+
+### Migration from v24 to v25
+
+-   remove deprecated components, properties and imports from your project, if the info cannot be found here then it was already mentioned in **Deprecated** sections of the v24.* changelogs.
+    -   we changed the integration of the supported react flow versions, formerly names `legacy` and `next` resources were renamed to more precise `v9` and `v10`, please see all info in the section about changes
+
 ## [24.1.0] - 2025-04-16
 
 ### Added

README.md

@@ -125,7 +125,7 @@ After you tested the GUI elements package locally you can Clean up your applicat
 3. Pull request from release branch into `main` need to be approved
     - then ["Publish: final release "](https://github.com/eccenca/gui-elements/actions/workflows/publish-final-release.yml) can be used on `main` (or `next` and `legacy`) to publish final release packages
     - another PR is automatically created for changes done during publishing process
-
+ 
 ## License
 
 Apache License, Version 2.0, January 2004