Skip to content
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

Switch to go-ipfs 0.5.1 #1500

Closed
lidel opened this issue May 12, 2020 · 1 comment · Fixed by #1501
Closed

Switch to go-ipfs 0.5.1 #1500

lidel opened this issue May 12, 2020 · 1 comment · Fixed by #1501
Assignees
Labels
effort/hours Estimated to take one or several hours exp/novice Someone with a little familiarity can pick up kind/maintenance Work required to avoid breaking changes or harm to project's status quo P0 Critical: Tackled by core team ASAP status/in-progress In progress

Comments

@lidel
Copy link
Member

lidel commented May 12, 2020

We should release ipfs-desktop v0.11.3 with go-ipfs v0.5.1
Ref. https://github.com/ipfs/go-ipfs/releases/tag/v0.5.1

Note: this depends on https://www.npmjs.com/package/go-ipfs-dep being updated to 0.5.1 first, which should happen automatically within 1-2h after https://dist.ipfs.io is updated. If its not at 0.5.1 tomorrow, we need to look into why automatic publishing failed.

@lidel lidel added exp/novice Someone with a little familiarity can pick up P0 Critical: Tackled by core team ASAP kind/maintenance Work required to avoid breaking changes or harm to project's status quo effort/hours Estimated to take one or several hours status/in-progress In progress labels May 12, 2020
@bertrandfalguiere
Copy link
Contributor

If you son't mind updating the translations at the same time... :)

#1415 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours exp/novice Someone with a little familiarity can pick up kind/maintenance Work required to avoid breaking changes or harm to project's status quo P0 Critical: Tackled by core team ASAP status/in-progress In progress
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants