vscode-haskell
vscode-haskell copied to clipboard
Prepare release 2.6.0
Release Checklist
- [x] Run
yarn auditfor security vulnerabilities.- Fix vulnerabilities.
- [x] Run
yarn outdatedto find outdated package version, review what needs to be updated.yarn upgrade-interactiveandyarn upgrade-interactive --latestis helpful here.
- [x] Run
cat test/testdata/schema/*/vscode-extension-schema.golden.json | jq --sort-keys -s addin thehaskell-language-serverrepo and add new configuration items. - [x] 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.patchfor release versions andmajor.ODD_NUMBER.patchfor pre-release versions. For example:2.0.*for release and2.1.*for pre-release.
- For pre-releases, we follow the version convention at: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#prerelease-extensions. We use
- [x] Update ChangeLog.md. The output of
./GenChangelogs.hsusually suffices. - [x] Update the README.md to have no outdated information.
- [x] Make sure CI is succeeding.
- [ ] Perform the release by creating a release in Github
- Github actions will automatically release the extension to VSCode- and VSX-Marketplace.
- If you want to create a pre-release, create a pre-release in Github. The github action will perform the appropriate actions automatically and publish the pre-release of the extension to VSCode- and VSX-Marketplace.
Notable changes
- Enables the
hls-cabal-pluginfor all users. - Adds
cabalFormattingProvideroption.
I will likely wait a little bit to merge this until the HLS release 2.9.0.0 is finished.
Is there any blocker on this release?
No, I just didn't get to it since the ghcup release of HLS.
@konn Fyi, release is finally happening :)