v2 is used so that the import path is different. The idea is that by breaking the API, you are basically making a new module instead of improving one (metaphorically of course), and it doesn't make sense for the same module to have the same import path.
If you want to change the import path and also release a new version, then simply changing the import path is enough. No need to put v2.
See it as them releasing a totally new package that just happens to have the same name, if that helps.
If you want to change the import path and also release a new version, then simply changing the import path is enough. No need to put v2.
See it as them releasing a totally new package that just happens to have the same name, if that helps.