Consider relaxing minimum go requirement

[psafont]

Hi, I saw a post in lobsters about this project and I wanted to try it out.

On my workstation, Fedora 43 is installed, which provides go 1.15.9, but a dependabot commit raised the requirement to 1.16.0 some weeks ago: ed7c9a7

This means that running the install instructions generates an error:

go install github.com/git-pkgs/forge/cmd/forge@latest
go: downloading github.com/git-pkgs/forge v0.4.0
go: github.com/git-pkgs/forge/cmd/forge@latest: github.com/git-pkgs/forge@v0.4.0 requires go >= 1.26 (running go 1.25.9; GOTOOLCHAIN=local)

I was able to try the tool by forcing the installation of a commit:

go install github.com/git-pkgs/forge/cmd/forge@95c191e83e9b9fe4ffc0b27398bc42dd12a16a02

I didn't see any comment in the related PR about the version of go, so I was wondering if this was intentional, or you would consider lowering the required go version to make the out-of-the-box experience better for more users.

Thank you for spending time on the project, it's especially timely now that gh added telemetry by default :)

[andrew]

@psafont happy to roll it back, would you be up for opening a PR?

[hramrach]

The Gitea SDK is aggressive with exploiting new go features, and requires recent go.

Interestingly, on the 'stable' distributions I care about it is available but it might have something to do with buy-in into Gitea as forge for managing the distribution sources.

Is building current go with the distribution go so much of a problem?

Understandably the experience varies depending on the distribution and the investment into tools that empower users to expand the distribution.