You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result of the move to submodules go install github.com/ipfs/fs-repo-migrations will target v1.7.1 since it was the last binary version to be present in that module. The fs-repo-migrations binary is now in a fs-repo-migrations subfolder+module. This means it needs to be installed as go install github.com/ipfs/fs-repo-migrations/fs-repo-migrations.
Unfortunately, there's not currently a tag for fs-repo-migrations/v2.0.2 so it will just pull the latest commit.
We should either:
Move fs-repo-migrations back to the root module and retag the root (e.g. v2.0.3)
Tag fs-repo-migrations/v2.0.3
Whichever we do should be documented in the README
The text was updated successfully, but these errors were encountered:
Speaking strictly for myself, I'd prefer a new tag, but I'm also fine with a comment in the README telling the user to run go install github.com/ipfs/fs-repo-migrations/fs-repo-migrations instead. So long as one doesn't need to wade eternally through the issues to figure out how to do it... 😸
As a result of the move to submodules
go install github.com/ipfs/fs-repo-migrations
will target v1.7.1 since it was the last binary version to be present in that module. Thefs-repo-migrations
binary is now in afs-repo-migrations
subfolder+module. This means it needs to be installed asgo install github.com/ipfs/fs-repo-migrations/fs-repo-migrations
.Unfortunately, there's not currently a tag for
fs-repo-migrations/v2.0.2
so it will just pull the latest commit.We should either:
fs-repo-migrations/v2.0.3
Whichever we do should be documented in the README
The text was updated successfully, but these errors were encountered: