Tags: clangd/vscode-clangd
Tags
Update release workflow to allow publishing pre-releases to the VSCod… …e Marketplace and OpenVSX (#777) Both VSCode Marketplace and OpenVSX have a concept of "pre-releases", versions of an VSCode extension which can be published to these marketplaces but only installed for users who opt into receiving pre-release versions. Using this mechanism provides a more robust way of validating new changes to vscode-clangd before pushing them out to all users in a stable release. The workflow considers anything with an odd minor version number (e.g. 0.1.34) to be a pre-release, while anything with an even minor version number (e.g. 0.2.0) will be a stable release. This allows us to control the type of release by bumping the version number appropriately. Fixes #765
Add an option to allow "clangd.path" to point to a shell script In VSCode 1.92 and later (which uses node 20), this requires passing `shell: true` in the executable options. However, using `shell: true` changes the behavior in some other ways, e.g. the path and arguments now have to be quoted in case they contain spaces. To avoid the potential for regressions from using `shell: true`, its use is made conditional on a new clangd option, "clangd.useScriptAsExecutable". Fixes #683
PreviousNext