Prepare 0.5.0 release - #129
Merged
Merged
Conversation
Member
Author
|
CI will be fixed by #130 |
Member
|
Sounds good to me, thank you! |
eldruin
force-pushed
the
prepare-release-0.5.0
branch
from
August 21, 2026 11:01
b54f1e5 to
463102d
Compare
Member
Author
Sure. Only two deprecation warnings to fix: #131 |
eldruin
force-pushed
the
prepare-release-0.5.0
branch
from
August 24, 2026 09:04
463102d to
40a5d01
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In #128 a new release was requested several months ago.
I'm not aware of any blocker we should wait for.However, CI errors need to be fixed, first.