Angular 18.2.3 support

Hi, is there a date planned when angular 18.2.3 will be supported?

I saw 6.1 is for ^17.0.0 but when i npm install i only get this errors:

npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: mdb-angular-ui-kit@6.1.0 npm ERR! Found: @angular/animations@18.2.3 npm ERR! node_modules/@angular/animations npm ERR! @angular/animations@"18.2.3" from the root project npm ERR! peerOptional @angular/animations@"18.2.3" from @angular/platform-browser@18.2.3 npm ERR! node_modules/@angular/platform-browser npm ERR! @angular/platform-browser@"18.2.3" from the root project npm ERR! peer @angular/platform-browser@"18.2.3" from @angular/forms@18.2.3 npm ERR! node_modules/@angular/forms npm ERR! @angular/forms@"18.2.3" from the root project npm ERR! 2 more (survey-angular-ui, survey-creator-angular) npm ERR! 2 more (@angular/platform-browser-dynamic, @angular/router) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @angular/animations@"^17.0.0" from mdb-angular-ui-kit@6.1.0 npm ERR! node_modules/mdb-angular-ui-kit npm ERR! mdb-angular-ui-kit@"file:mdb-angular-ui-kit-6.1.0.tgz" from the root project npm ERR! peer mdb-angular-ui-kit@"^6.0.0" from mdb-angular-wysiwyg@6.0.0 npm ERR! node_modules/mdb-angular-wysiwyg npm ERR! mdb-angular-wysiwyg@"git+https://oauth2:DAfvmmk-rVpesAzfYQ6y@git.mdbootstrap.com/mdb/angular/mdb5/plugins/prd/wysiwyg" from the root project npm ERR! npm ERR! Conflicting peer dependency: @angular/animations@17.3.12 npm ERR! node_modules/@angular/animations npm ERR! peer @angular/animations@"^17.0.0" from mdb-angular-ui-kit@6.1.0 npm ERR! node_modules/mdb-angular-ui-kit npm ERR! mdb-angular-ui-kit@"file:mdb-angular-ui-kit-6.1.0.tgz" from the root project npm ERR! peer mdb-angular-ui-kit@"^6.0.0" from mdb-angular-wysiwyg@6.0.0 npm ERR! node_modules/mdb-angular-wysiwyg npm ERR! mdb-angular-wysiwyg@"git+https://oauth2:DAfvmmk-rVpesAzfYQ6y@git.mdbootstrap.com/mdb/angular/mdb5/plugins/prd/wysiwyg" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.