top-level go directive in go.mod is now unnecessarily restrictive?

[dnwe]

Since #3410 the go directive in the top-level go.mod for the go-github library was bumped to an absolute of 1.22.10 here which now requires all consumers to be building with the latest 1.22.10 release of Go 1.22 — this seems unnecessarily restrictive for a library module, particularly as the code itself doesn't currently use any modern language constructs and builds fine even with Go 1.19. Could we at least relax the go directive to 1.22.0 on the assumption that you're doing it to only support the latest N-1 and N releases of the Go toolchain?

[dnwe]

(@gmlewis FYI)

[gmlewis]

@dnwe - yes, there have been several discussions about this before we changed this, and this is the first feedback we have received.

I have no problem with a more relaxed directive to revert back to former behavior.

Please submit a PR that satisfies your requirements.

[gmlewis]

Please make sure to update the README.md clearly stating the policy you would like us to adhere to, moving forward.

[dnwe]

Raised #3423 with a proposal