On the topic of updating the go version for gocql. As the recent maintainer, Martin Sucha, mentioned:
> In our README, we state: >> In general, the Cassandra community will focus on supporting the current and previous versions of Go. > So it should be safe to bump to 1.22. However, it should be considered that some (legacy) projects may want to use new gocql features without upgrading their go version. Users on go 1.19–1.21 would need to upgrade, which may not be feasible for all. It would be beneficial to research the versions used by other projects that depend on gocql. This way, we can make a better decision, aiming to adopt the latest features while balancing compatibility. Taking the current state, bumping to go 1.19 seems the most balanced for now: - It meets our current technical requirement (atomic.Bool). - It minimizes disruptions by supporting a broader range of users who are still migrating to newer versions of go. For now, it might make sense to keep in mind to upgrade the minimum requirement at go 1.19 and only revisit this when we have strong arguments to upgrade further, perhaps around the gocql 2.0 release. There's also a good discussion on this topic in slack: https://the-asf.slack.com/archives/C05LPRVNZV1/p1725459369234389
