<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=550415) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "feature" label: - https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues?label_name%5B%5D=type%3A%3Afeature and verify the issue you're about to submit isn't a duplicate. ---> ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> Currently we change the minimum version of the relevant IDE for extensions approximately every 3 months meaning that we support IDEs roughly 12 months old. For certain customers it can be challenging to roll out newer IDE releases quickly enough so that they can keep track of our extension upgrades. This can lead to extensions being automatically upgraded on IDE versions that are not supported and lead to user frustration. ### Proposal Clearer communication around upcoming IDE version deprecations and a more gradual transition path would be extremely helpful. ### Further details <!-- Include examples, use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Links / references