chore: update NestJS dependency to v11

[estiller]

Update the NestJS dependency to use v11.
This should solve #862 regarding issues with peer dependencies in NestJS.

[wing328]

build failed:

error @nestjs/[email protected]: The engine "node" is incompatible with this module. Expected version ">= 20". Got "18.20.5"

given that node 18 is still supported, I think we will need to delay the upgrade for at least a few months: https://endoflife.date/nodejs

[MathieuGuillet]

given that node 18 is still supported, I think we will need to delay the upgrade for at least a few months: https://endoflife.date/nodejs

Hello @wing328 👋
I understand your concern about retrocompatibility. But as node 18 maintenance will stop in next April, the projects that are still using it will have to upgrade eventually. They can still stick to the current version until then, can't they?

This current dependency to nest v10 is blocking a whole chain of dependency update on my project, and I think that we are not the only one in that case.
Is it possible to merge this PR and deliver a new version of openapi-generator-cli ?
Thanks 🙏

[MathieuGuillet]

Hello @wing328 👋,
any new considerations concerning for this PR ?
Thanks

[wing328]

please resolve the merge conflicts, update CI to test with node v20 so that all tests pass

then I'll get it merged :)

[MathieuGuillet]

Hello @estiller !
Would you have a moment to resolve the conflicts on this PR ? I would help if I can, but I do not have the permission.
Many thanks 👍

[estiller]

Here you go

[MathieuGuillet]

Hello @wing328 !
This PR is ready to be merged 🎉 🙏
Thank you so much @estiller !

[wing328]

thank you. will merge once all tests pass

[github-actions]

🎉 This PR is included in version 2.19.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[wing328]

@estiller thanks again for the PR, which has been merged and released.

Quick question: do we need to update @type/node to v20.x as well?

related pr: #907

[wing328]

fyi. did a test locally and the result is good

C:\Users\wing3>npm uninstall -g @openapitools/openapi-generator-cli

up to date in 657ms

C:\Users\wing3>npm install -g @openapitools/openapi-generator-cli

added 162 packages in 21s

36 packages are looking for funding
  run `npm fund` for details

C:\Users\wing3>openapi-generator-cli generate -g ruby -i https://raw.githubusercontent.com/OpenAPITools/openapi-generator/master/modules/openapi-generator/src/test/resources/3_0/petstore.yaml -o C:\temp\ruby-client
Download 7.11.0 ...
Downloaded 7.11.0
[main] INFO  o.o.codegen.DefaultGenerator - Generating with dryRun=false
[main] INFO  o.o.codegen.DefaultGenerator - OpenAPI Generator: ruby (client)
[main] INFO  o.o.codegen.DefaultGenerator - Generator 'ruby' is considered stable.

[estiller]

@estiller thanks again for the PR, which has been merged and released.

Quick question: do we need to update @type/node to v20.x as well?

related pr: #907

It's probably a good idea, regardless of this change, if support is dropped for v18.

[wing328]

do you mind filing a PR for that when you've time? 🙏

[estiller]

do you mind filing a PR for that when you've time? 🙏

#911