Closed msteinert closed 1 year ago
Wow... That's weird, so should we move to a v2 folder or do you instead want to do a non-as-major release instead?
Hmm, I'm not sure. I need to reread that series of blog posts and think about it a bit. Maintaining two versions feels like a lot of work for this particular project. At the same time I would feel bad breaking the API. I might try to take a look at how other projects are handling this too.
Let me know what you think.
I think this might be the model to follow: https://github.com/jackc/pgx
If I understand correctly, the module name is updated in go.mod
, then the older version is maintained on a branch.
Fixed by #21
Apparently v2 tags are not supported.
https://go.dev/blog/v2-go-modules
This issue is a reminder to follow up on a v2 release as described in the link.