Prepare pre-release 2.5.2 (#1032)

Changelog.md

@@ -1,5 +1,9 @@
 # Changelog for vscode-haskell
 
+## 2.5.2
+
+- Includes changes of the 2.4.3 release
+
 ## 2.5.1
 
 - Includes changes of the 2.4.2 release
@@ -9,6 +13,13 @@
 - Add tracking of cabal files
   ([#618](https://github.com/haskell/vscode-haskell/pull/618))  by @fendor
 
+## 2.4.3
+
+- Address invalid byte sequence error #1022
+  ([#1022](https://github.com/haskell/vscode-haskell/pull/1022))  by @felixlinker
+- Always set the cwd for the executable (#1011)
+  ([#1011](https://github.com/haskell/vscode-haskell/pull/1011))  by @fendor
+
 ## 2.4.2
 
 - Add stan plugin option #1000

docs/Release.md

@@ -6,7 +6,7 @@ Follow this list for items that must be completed for release of the `vscode-has
   - Fix vulnerabilities.
 - [ ] Run `yarn outdated` to find outdated package version, review what needs to be updated.
   - `yarn upgrade-interactive` and `yarn upgrade-interactive --latest` is helpful here.
-- [ ] Run `haskell-language-server vscode-extension-schema` with the latest `haskell-language-server` to check if there have new fields.
+- [ ] Run `cat test/testdata/schema/*/vscode-extension-schema.golden.json | jq --sort-keys -s add` in the `haskell-language-server` repo and add new configuration items.
 - [ ] SemVer Compatible Version Bump in `package.json`
   - For pre-releases, we follow the version convention at: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions. We use `major.EVEN_NUMBER.patch` for release versions and `major.ODD_NUMBER.patch` for pre-release versions. For example: `2.0.*` for release and `2.1.*` for pre-release.
 - [ ] Update ChangeLog.md. The output of `./GenChangelogs.hs` usually suffices.