Ext folder preventing module update

[hjwalt]

Issue description

Package rename should not happen within the same major version as it is not backward compatible

Example code

go.mod

...
require (
...
  github.com/ClickHouse/clickhouse-go/v2 v2.0.11
...
)
...

Run

go get -u ./...

Error log

github.com/me/my-repo imports
        github.com/ClickHouse/clickhouse-go/v2 imports
        github.com/ClickHouse/clickhouse-go/v2/ext: cannot find module providing package github.com/ClickHouse/clickhouse-go/v2/ext

Configuration

OS: MacOS Monterey

Interface: native

Driver version: v2.0.11

Go version: 1.18.1 darwin/arm64

ClickHouse Server version: N/A

[hjwalt]

@gingerwizard is the rename something we want in version 2? if so can we release a new version with the ext rename so it doesn't block module upgrades with go get -u?

[gingerwizard]

Thankis @hjwalt for raising and spotting this. It seemed we have a broken release https://pkg.go.dev/github.com/ClickHouse/clickhouse-go/v2@v2.0.13

2.0.13 is effectively broken but we've released v2.0.14. 2.0.13 is unfortunately permanently broken - I'm not sure we can update pkg - afaik this is immutable.

There is the wider question of this being a breaking change inside a major. Yes this PR was eagerly merged and we should have maybe discussed with the community. We apologise. I'm hesitant to revert this PR as its a long time before we plan to cut a v3. We will be more diligent in future and avoid this sort of mess.

[hjwalt]

Thank you for your help @gingerwizard ! This will unblock what I'm doing.

It is not really breaking from my side in that case then as I don't use the ext / external package. I thought the rename breaks the upgrade path, but it doesn't seem to be the case then.