[PLACEHOLDER] Graceful VS Code extension version handling in the integration (deep-linking) scenario

[petrhollayms]

We need to ensure that the TTK (and other) extension and Kiota extension work smoothly even when one is upgraded to a new version. We want to follow the Semantic versioning approach.

Open questions:

• Define approach for handling the UX consistency across minor versions
• Define mechanism to coordinate the release of major versions between both/all teams
• Decide how to handle the situation on the client side when the user upgrades one extension to the new major version only. Enforce the upgrade of the second one?

Proposal for the handling (to be completed):

• All minor/patch versions in the same major versions shall work end-to-end.

[maisarissi]

As I mentioned in the other issue, I'm not sure we need to check version installed as VS Code extension always gets updated automatically to the latest version. What's your proposal here?

[maisarissi]

Is there anything else we need to do to address this?

[baywet]

closing since we have now pivoted to shipping an npm package instead which the consumers can pin the version of