Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare release 2.4.3 #1031

Merged
merged 1 commit into from
Jan 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions Changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,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
Expand Down
2 changes: 1 addition & 1 deletion docs/Release.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading