At the moment there is no strict correspondence between version of Devspaces Code and VS Code version. 
The cause of the problem is - current state of Che-Code is taken when we are doing Eclipse Che / Dev Spaces release.
The proposal is: we should take the last commit of a released version of VS Code to release some version of the Devspaces Code. 

For example, the last commit of 1.86.0 version of VS Code is: this one, see info here.
So, to prepare 3.11 (just for example) version of Devspaces Code we should take Che-Code state with this commit, no other commits from VS Code should be present in the released branch of the Che-Code.

As result we will know exactly that 3.11 version of Devspaces Code is based on the 1.86.0 version of VS Code. Also the given assembly will be more reliable as it will contain released version of VS Code - so - more stable assembly.