TL;DR: importing badger v2.0.0 requires using Go modules, let us know if this is a big deal for your project
Hi there, friends of the badger!
I wanted to give an early warning to all of you using Badger and planning to migrate to v2.0.0 as soon as it comes out in a couple of days.
The latest and best version of Badger uses Go modules, as requested by a large part of our community. Unfortunately, dep and many other dependency management tools have not been adapted to Go Modules and specifically aren’t able to handle the versioned import paths such as
Badger v2.0.0 will not be supported for those not on Go modules
We expect the Go team to work on this situation and at least finalize the proposed change in this PR.
So, what do you have to do to adopt Badger v2?
- if you’re already using Go modules, you’re good!
- if you’re using dep, you will need to migrate to Go modules or find a temporary workaround (please share!)
For those using other dependency management tools, they might or might not support Go modules - all of the ones we tried (govendor, glide, dep, godep) did not support this.
If your team would be impacted by this, as you were counting on migrating to v2 soon but you can’t adopt Go modules yet, please let us know and we’ll try to figure out how to support your usecase. You can get in touch with me directly at firstname.lastname@example.org.
Thanks in advance,