-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update multiaddr to the latest version 馃殌 #67
base: master
Are you sure you want to change the base?
Conversation
Version 2.3.0 just got published. |
Version 3.0.0 just got published. |
Version 3.0.1 just got published. |
Version 3.0.2 just got published.Update to this version instead 馃殌 Release Notesv3.0.2FeaturesCommitsThe new version differs by 8 commits.
See the full diff |
Version 3.1.0 just got published.Update to this version instead 馃殌 Release Notesv3.1.0Bug FixesCommitsThe new version differs by 9 commits.
See the full diff |
Version 3.2.0 just got published.Update to this version instead 馃殌 Release Notesv3.2.0Features |
Version 4.0.0 just got published. |
Version 5.0.0 just got published. |
Update to this version instead 馃殌 CommitsThe new version differs by 12 commits.
See the full diff |
Update to this version instead 馃殌 Release Notes for v6.0.0Bug FixesFeatures
BREAKING CHANGES
The UDP code is now |
|
|
Update to this version instead 馃殌 Release Notes for v6.0.3Bug FixesCommitsThe new version differs by 9 commits.
See the full diff |
Update to this version instead 馃殌 Release Notes for v6.0.4Features
|
Update to this version instead 馃殌 Release Notes for v6.0.5FeaturesCommitsThe new version differs by 7 commits.
See the full diff |
|
|
|
|
|
|
|
|
|
|
|
|
Version 2.2.3 of multiaddr just got published.
The version 2.2.3 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of multiaddr.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 5 commits .
d632745
chore: release version v2.2.3
1939b35
chore: update contributors
cbfcbdb
chore: update deps
08d5d5d
[WIP] feat: adding p2p-circuit proto (#41)
e7e53b9
test: use dirty-chai
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨