Go module versioning

[faddat]

For reasons that I don't yet understand, we have moved the main branch back to v7.

This is making reviews and contributions a bit more complicated for me, and I just wanted to know why that was done

[hleb-albau]

can we use v9 for now?

[faddat]

@hleb-albau I don't know, that's actually the reason for this issue. Just seeking guidance on how to use the module version paths currently.

[p0mvn]

I think it's time to do this. Our main branch is still on v7. What do others think? I can create a PR today if we are good with this

[ValarDragon]

Sure, please go for it. If you have time, want to also add a manually triggerable github workflow to do the find/replace to update all imports? (And then we can just manually trigger that for open PRs for now)

[p0mvn]

Sounds good, on it

[p0mvn]

The manual workflow is now in. However, the rest of the CI does not auto-run from the pull request triggered by the workflow (example #2096). The reason is a Github security limitation, ref: peter-evans/create-pull-request#48

One of the manual solutions is to close and reopen a PR (example #2101). There are more automatic solutions that are listed here: peter-evans/create-pull-request#48

Unfortunately, the currently chosen Github Action does not support any suggested automatic solutions. We would either have to fork the existing action and modify it or switch to: https://github.com/peter-evans/create-pull-request

I think closing and reopening to trigger CI is fine for the time being. This workflow is not meant to be run regularly anyways (only on major releases).

I'm still open to changing the action if it proves to be troublesome