Release 0.3.2 (#876)

Release 0.3.1 (#858)

No functional changes since 0.3.0, just need to trigger the release workflow again as it failed for 0.3.0.

Release 0.2.0 (#817)

Release 0.1.35

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

Add a Github workflow for creating an unstable release (#748)

The workflow is manually triggered, and creates a Github
release containing a build from the master branch.

Revert #730 and release 0.1.33 (#736)

This reverts commit ea588aa.

Release version 0.1.32 (#732)

Revert #708 and #715, and release 0.1.31 (#724)

This reverts commits 4f64ca7 (#715) and 0c2d40d (#708).