feat(api): enforce max cli version

[bodinsamuel]

Describe your changes

Fixes https://linear.app/nango/issue/NAN-2097/enforce-maximum-cli-version-on-public-api

Note

This is a proposal

• Enforce a maximum CLI version tied to the backend version
  It's usually not an issue. But on cloud it's problematic:
• if people upgrade their CLI and we rollback
• if we deploy runner and not server
  For enterprises it's worse because they are pinned to a version for months and it's easy to make the mistake of upgrading the CLI but not the backend.

This might be too strict, I'm not sure. let me know

[linear]

NAN-2097 Enforce maximum CLI version on public API

[TBonnin]

I like the idea, especially for enterprise customers.

[bodinsamuel]

As discussed with bastien, I might try to enforce only minor versions instead of patch so we can still provide patches for enterprise (eventually) <=0.42.xxx

[TBonnin]

As discussed with bastien, I might try to enforce only minor versions instead of patch so we can still provide patches for enterprise (eventually) <=0.42.xxx

It would then only be useful if we follow proper semantic versioning, which limits a lot the safeguard capability this change is supposed to provide

[bodinsamuel]

It would then only be useful if we follow proper semantic versioning, which limits a lot the safeguard capability this change is supposed to provide

Yeah that's my fear, also I'm not sure we have a way to backfill patches so it's limited.

[khaliqgant]

We should start to follow proper semantic versioning in this case.