Upgrading actions/upload-artifact@v2 to v4 breaks the generation the Vscode extension in the pipeline because this new version doesn't allow the artifacts exported by the pipeline to have the same name (previous was to replace existing artifacts).
To fix this, a separate job is dedicated to the generation of the Vscode extension independently from OCaml version which avoids multiple generations.
Besides, the nodejs version has been upgrated to newest version (up to 20)
Upgrading actions/upload-artifact@v2 to v4 breaks the generation the Vscode extension in the pipeline because this new version doesn't allow the artifacts exported by the pipeline to have the same name (previous was to replace existing artifacts).
To fix this, a separate job is dedicated to the generation of the Vscode extension independently from OCaml version which avoids multiple generations.
Besides, the nodejs version has been upgrated to newest version (up to 20)