[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)
Developer checklist
[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.
Testing checklist
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
QA Steps
Screenshots (if available)
How to merge
Send the message bors r+ to merge this PR. For more information, see
docs/how-to/bors.md.
Previous revision accidentally included a bogus bound on network-transport (> 1.0, which does not exist). Not sure how that happened.
https://github.com/avieth/network-transport-tcp/commit/613332da47e2c3e4a79017ca188c9e6568671222
Description
Linked issue
Type of change
Developer checklist
Testing checklist
QA Steps
Screenshots (if available)
How to merge
Send the message
bors r+
to merge this PR. For more information, seedocs/how-to/bors.md
.