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 version upgrade #107

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Go version upgrade #107

merged 1 commit into from
Dec 19, 2024

Conversation

cceckman
Copy link
Collaborator

  • chore: go module upgrade
  • chore: upgrade go version

Since apparently the just-module rev didn't build.

@jdkaplan
Copy link
Collaborator

jdkaplan commented Dec 19, 2024

Happened to see this one, so I can put my stamp on it 😛

I noticed that deploys started failing after the (not technically necessary?) golang.org/x/crypto update in #105, but I haven't had a chance to look into it. A full upgrade sweep can't hurt though 🙂

@cceckman cceckman merged commit d20cf6e into main Dec 19, 2024
3 checks passed
@cceckman cceckman deleted the upgrades branch December 19, 2024 23:11
@cceckman
Copy link
Collaborator Author

Yeah - I just wanted to get through the dependabot noise.

The builder was failing with:

/workspace/go.mod:3: invalid go version '1.22.7': must match format 1.23

Which...I dunno, did that change? I don't think we manually edited it.

But, whatever let's see if this works...

cceckman added a commit that referenced this pull request Dec 20, 2024
cceckman added a commit that referenced this pull request Dec 20, 2024
-   Reverts prior changes (upgrade to 1.23 #107, `go get -u` #106),
    as 1.23 is not yet supported by the cloudbuild script.
-   Upgrade gRPC, due to missing go.sum entries in the stack.
-   Use `go mod tidy -go=1.22` to clean things up.
-   Read and specify the builder version in the cloudbuild files.
    The worker had been defaulting to 1.15, which didn't support
    point releases in module declarations.

Tested on the dev environment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants