This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
Update libp2p-ipfs-browser to version 0.13.0 🚀 #457
Closed
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
daviddias
added
milestone 2
and removed
milestone 2
status/deferred
|
update manually |
MicrowaveDev
pushed a commit
to galtproject/js-ipfs
that referenced
this pull request
May 22, 2020
(breaks on my linux system as case sensitive)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hello lovely humans,
libp2p-ipfs-browser just published its new version 0.13.0.
This version 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 libp2p-ipfs-browser.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 11 commits .
1f59390chore: release version v0.13.06d0428achore: update contributors16ad893Merge pull request #84 from ipfs/pull716e738update to the latest deps and fix tests734bc4crefactor: use pull-streams0eabb18Merge pull request #87 from ipfs/greenkeeper-aegir-8.0.0ba6c475chore(package): update aegir to version 8.0.0950a9adMerge pull request #80 from ipfs/greenkeeper-aegir-6.0.024508fcchore(package): update aegir to version 6.0.068a9b34Merge pull request #79 from ipfs/greenkeeper-aegir-5.0.122dafd5chore(package): update aegir to version 5.0.1See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade