Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go.mod: Tidy with Go 1.19 #471

Merged
merged 1 commit into from
Aug 1, 2023
Merged

go.mod: Tidy with Go 1.19 #471

merged 1 commit into from
Aug 1, 2023

Conversation

abhinav
Copy link
Contributor

@abhinav abhinav commented Aug 1, 2023

Runs go mod tidy with -go=1.19 on the go.mod for the project.
Note that as of Go 1.20, the go directive is not
the minimum required Go version.
It's the version of the toolchain we developed against.
This is changing in Go 1.21.

The -compat flag specifies which version of Go the go.mod file
needs to be compatible with.
By default, this is one release behind the -go flag
(or go directive).
So we don't need to specify it manually.

Lastly, this deletes the go mod tidy in the test job.
Only the lint job should bbe modifying the go.mod
to ensure that the go.mod is up to date.

@abhinav abhinav added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Aug 1, 2023
This was referenced Aug 1, 2023
Copy link
Contributor Author

abhinav commented Aug 1, 2023

@abhinav abhinav requested a review from a team August 1, 2023 19:12
Base automatically changed from abhinav/go120 to main August 1, 2023 19:44
@abhinav abhinav enabled auto-merge (squash) August 1, 2023 20:06
Runs `go mod tidy` with -go=1.19 on the go.mod for the project.
Note that as of Go 1.20, the `go` directive is **not**
the minimum required Go version.
It's the version of the toolchain we developed against.
This is changing in Go 1.21.

The `-compat` flag specifies which version of Go the go.mod file
needs to be compatible with.
By default, this is one release behind the `-go` flag
(or `go` directive).
So we don't need to specify it manually.

Lastly, this deletes the `go mod tidy` in the test job.
Only the lint job should bbe modifying the go.mod
to ensure that the go.mod is up to date.
@abhinav abhinav changed the base branch from main to abhinav/pulumi-up August 1, 2023 20:37
@abhinav abhinav merged commit 3e49ad9 into abhinav/pulumi-up Aug 1, 2023
2 checks passed
@abhinav abhinav deleted the abhinav/tidy branch August 1, 2023 20:37
@abhinav
Copy link
Contributor Author

abhinav commented Aug 1, 2023

Oops. This was not intended to be merged into the other branch.

@abhinav abhinav mentioned this pull request Aug 1, 2023
abhinav added a commit that referenced this pull request Aug 1, 2023
Runs `go mod tidy` with -go=1.19 on the go.mod for the project.
Note that as of Go 1.20, the `go` directive is **not**
the minimum required Go version.
It's the version of the toolchain we developed against.
This is changing in Go 1.21.

The `-compat` flag specifies which version of Go the go.mod file
needs to be compatible with.
By default, this is one release behind the `-go` flag
(or `go` directive).
So we don't need to specify it manually.

Lastly, this deletes the `go mod tidy` in the test job.
Only the lint job should bbe modifying the go.mod
to ensure that the go.mod is up to date.

(This is a copy of #471, which was accidentally merged into #474.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant