Release 0.6.8 #3165
Merged
Release 0.6.8 #3165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The CHANGELOG generator we use: https://github.com/github-changelog-generator/github-changelog-generator has stopped working with errors like the following: Warning: PR 3148 merge commit was not found in the release branch or tagged git history and no rebased SHA comment was found So we'll defer populating the CHANGELOG summary until after the release
paulcadman
force-pushed
the
release-0.6.8
branch
from
5d03122 to
8beaee7
Compare
lukaszcz
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this release is to add support for the
--vscodeflag, required by an update to the juvix vscode extension.--vscodeoption #3162This PR updates:
The CHANGELOG generator we use:
https://github.com/github-changelog-generator/github-changelog-generator
has stopped working with errors like the following:
So we'll defer populating the CHANGELOG summary until after the release.