-
Notifications
You must be signed in to change notification settings - Fork 866
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: show repo migration (go-ipfs 0.12.0) #1982
Conversation
This comment was marked as spam.
This comment was marked as spam.
I will try to include #1823 in this PR too. |
@lidel can you please take a look? it should be ready |
this also decreases the interval to make it more snappy
380fa84
to
062e0c9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @hacdias!
Did some testing with 0.11 → 0.12 and UX should be more than enough for users with big repos.
Merging, as we want to ship ipfs-desktop with 0.12 this week.
this ensures that migration window will be shown again on error or on success -- this way user who let it run in the background gets feedback when their node is available again
062e0c9
to
a7c4cb4
Compare
Hi, just passing by to describe an issue I just had. I installed the latest binary proposed go-ipfs_v0.11.0_linux-amd64.tar.gz and then wanted to have a look at the desktop version with ipfs-desktop-0.20.1-linux-amd64.deb which apparently installs v.0.12. Then trying to run daemon again I got Readme says
So I bascially deleted my config file and ipfs init again tu run go-ipfs version: 0.11.0 again. Thanks |
Hi @gRoussac! IPFS Desktop upgraded your repository to a newer version. You now need to update the binary you are using to run IPFS from 0.11 to 0.12. I created a PR to update the docs to the newer version: ipfs/ipfs-docs#1074 |
Thanks! |
Closes #1940 and closes #1823 + uses go-ipfs 0.12