Remove the description of the old go.mod specification

[178inaba]

Description:

Starting from Go 1.21, the go.mod file now includes patch versions as well.

$ go1.21.0 mod init test
go: creating new go.mod: module test
$ cat go.mod
module test

go 1.21.0

This is explained in the official Go documentation.

Go 1.21 introduces a small change to the numbering of releases. In the past, we used Go 1.N to refer to both the overall Go language version and release family as well as the first release in that family. Starting in Go 1.21, the first release is now Go 1.N.0. Today we are releasing both the Go 1.21 language and its initial implementation, the Go 1.21.0 release. These notes refer to “Go 1.21”; tools like go version will report “go1.21.0” (until you upgrade to Go 1.21.1). See “Go versions” in the “Go Toolchains” documentation for details about the new version numbering.
https://go.dev/doc/go1.21#introduction

setup-go retrieves the version of the go.mod file using the following code and can obtain the patch version as well.

setup-go/src/installer.ts

Line 427 in 6c1fd22

const match = contents.match(/^go (\d+(\.\d+)*)/m);

Test:

https://www.typescriptlang.org/play?#code/MYewdgzgLgBKZQKYIjAvDARAcxDAjAHQBMxhADJgNwBQ80MAtgIZTAAW6c4SKhLbdgAoA9AD1cMIQB0AJgGoZhOfICUAKlUjGq2vRAAbRIQMhsQgR10wYQA

Additionally, I fixed the following:

• Fix emoji rendering in contributors.md.
• Fix quoting in README.md.
• Remove the single quotes from go-version-file.

Related issue:

Fixes #461.

Check list:

• [ ] Mark if documentation changes are required.
• [ ] Mark if tests were added or updated to cover the changes.

This pull request is a documentation update itself. No testing is necessary.

[gowridurgad]

Hi @178inaba ,Could you please update the readme file with the below content, " The go-version-file input accepts a path to a go.mod file or a go.work file that contains the version of Go to be used by a project. The action will search for the latest available version sequentially in the runner's directory with the cached tools, in the [versions-manifest.json] (https://github.com/actions/go-versions/blob/main/versions- manifest.json) file or at the go servers." please add both with and without quotes here ,because both scenarios are working:
go-version-file: 'path/to/go.mod' or go-version-file: path/to/go.mod

[178inaba]

@gowridurgad
Thank you for the review!

The action will search for the latest available version sequentially in the runner's directory with the cached tools, in the versions-manifest.json file or at the go servers.

The go.mod file or go.work file now includes patch versions as well. Therefore, the version is fixed, and I thought there is no need to search for the latest version. Is this thinking incorrect?

please add both with and without quotes here ,because both scenarios are working:
go-version-file: 'path/to/go.mod' or go-version-file: path/to/go.mod

The README includes a section on 'cache-dependency-path', but it is not enclosed in quotes. Therefore, I thought it would be better to align with this.

setup-go/README.md

Lines 175 to 177 in be1aa11

	cache-dependency-path: |
	subdir/go.sum
	tools/go.sum

[ldemailly]

Searching for latest version is how it's been working before 1.22 / toolchain and I think it's the expected feature, I shouldn't need to keep changing my go.mod for a patch level and the go version in go.mod should be language version not a specific patch level (I complained as much in golang/go#66175 (comment))

[178inaba]

@ldemailly
Thank you for commenting!

In toolchains from version 1.21 onwards, there have been errors when running go mod tidy if the patch version is not specified. Therefore, it is believed that specifying the patch version is required.

$ cat go.mod
module test

go 1.22
$ go1.21.0 mod tidy
go: downloading go1.22 (darwin/amd64)
go: download go1.22 for darwin/amd64: toolchain not available

I've read several issue comments, and the corrective approach seems to be changing the error messages to prompt modifications to the go.mod files.

golang/go#66175 (comment)
golang/go#62278 (comment)

[aparnajyothi-y]

Hello @178inaba ,
Your reasoning makes sense ,The go.mod file or go.work file now includes patch versions as well. Therefore, the version is fixed, and there is no need to search for the latest version but If you want to allow flexibility for using newer patch versions without updating the go.mod or go.work file, the current behavior can be beneficial and The versions-manifest.json file can help ensure that the action uses a version of Go that's tested. This could be beneficial for ensuring compatibility and stability.so could please update the readme file.

[178inaba]

@aparnajyothi-y
Thank you for commenting!

I also verified that if I specified the toolchain as below, no error would occur with go mod tidy.

$ cat go.mod
module test

go 1.22

toolchain go1.22.0

In this case, setup-go will look for the latest patch version of 1.22.
Therefore, I will add this behavior to the README.

[178inaba]

I have added the following:

The `go` directive in `go.mod` can specify a patch version or omit it altogether (e.g., `go 1.22.0` or `go 1.22`).  
If a patch version is specified, that specific patch version will be used.  
If no patch version is specified, it will search for the latest available patch version in the cache,
[versions-manifest.json](https://github.com/actions/go-versions/blob/main/versions-manifest.json), and the
[official Go language website](https://golang.org/dl/?mode=json&include=all), in that order.

[gowridurgad]

Hi @178inaba, To avoid confusions, please revert this change or add both with and without quotes because both scenarios are working. go-version-file: 'path/to/go.mod' or go-version-file: path/to/go.mod

[178inaba]

@gowridurgad
I reverted!

[Mago16]

El El mar, 9 de abr de 2024 a la(s) 10:52 p.m., Priya Gupta < ***@***.***> escribió:

…

***@***.**** approved this pull request. — Reply to this email directly, view it on GitHub <#458 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX4MPLHBF4IKJVYIA4MWNRTY4TAQ7AVCNFSM6AAAAABDNNFWHCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSOJQG44TAOBSGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>