Prepare v1.1.2 release #83
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
|
@dget I will probably need your help to figure out how to publish this after it gets merged and tagged (and I fix the failing tests 😑) |
|
|
harto
force-pushed
the
prepare-v1.1.2
branch
6 times, most recently
from
92ee487 to
ece128f
Compare
harto
force-pushed
the
prepare-v1.1.2
branch
from
ece128f to
22abec4
Compare
harto
force-pushed
the
prepare-v1.1.2
branch
from
be1f7bb to
aeb7035
Compare
harto
force-pushed
the
prepare-v1.1.2
branch
from
aeb7035 to
1ccb390
Compare
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 wasn't sure if the changes (particularly #69 and #76) warranted more than a patch release. But since we don't pin dependency versions, this release seems no more or less compatible with v1.1.1 to me...
Related: #82