release 0.9 #1185
Merged
release 0.9 #1185
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
|
|
I still plan on doing that afterwords. As an aside: I don't know if the coverity upload token expired or something but coverity rate limiting us is why the CI is not working. Unfortunately I have no control over setting/updating that token. I might just have to disable that step. |
|
On Tue Apr 30, 2024 at 5:57 PM CEST, Randy Palamar wrote:
> ***@***.******@***.***%3E
I still plan on doing that afterwords.
Why afterwards? I don’t see any danger in it really (I have been running with the merged commits for the last couple of months and it just works).
|
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.
I tried to do a summary for the changelog instead of listing every last detail. Am I missing anything?