Release 0.14.1: Disable thread logging, reset resolver settings, pin raiden #937
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.
This sets up the version for a new release
0.14.1
Patch changes:
This fixes an issue when setting up
sentry
, where the gevent threading module monkeypatching wasn't completed, while thesentry
setup already generated log events with thread logging enabled.This also removes a patch from the DNS resolver, that lead to problems when trying to resolve addresses from a VPN NS from within docker.
Furthermore, the
raiden
dependency, formerly linked to thedevelop
at github, is now linked to a specific commit. This is done to remove version ambiguity for the next release ofraiden-services
.