prepare python release 0.6.1
#795
Merged
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
roeap
force-pushed
the
python-release-0.6.1
branch
from
f9dd88b
to
ce2f021
Compare
|
Thanks @fvaleye! What's next, just pushing a tag? Never did a release :). In any case, could you take care of that? |
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.
Description
Prepare the release of python version
0.6.1, to mitigate the regression regarding path handling.I tested it against real azure, azurite and localstack. Prettier made this PR a bit less pretty, but the following a re the relevant changes.
Related Issue(s)
closes #785 (i guess we'll see in ci :) ... but i could repro and fix it locally)
Documentation