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

use go 1.20 #288

Merged
merged 2 commits into from
Apr 16, 2024
Merged

use go 1.20 #288

merged 2 commits into from
Apr 16, 2024

Conversation

sophiewigmore
Copy link
Member

Summary

Upgrading to Go 1.21 has caused a number of failures in our various buildpacks. We should upgrade the Go versio eventually, but we should do it as a more organized effort

Use Cases

Checklist

  • I have viewed, signed, and submitted the Contributor License Agreement.
  • I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
  • I have added an integration test, if necessary.
  • I have reviewed the styleguide for guidance on my code quality.
  • I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@sophiewigmore sophiewigmore requested a review from a team as a code owner April 16, 2024 15:56
@sophiewigmore sophiewigmore added the semver:patch A change requiring a patch version bump label Apr 16, 2024
@sophiewigmore sophiewigmore enabled auto-merge (squash) April 16, 2024 18:56
@sophiewigmore sophiewigmore merged commit f23ed80 into main Apr 16, 2024
8 of 9 checks passed
@sophiewigmore sophiewigmore deleted the go-1.20 branch April 16, 2024 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch A change requiring a patch version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants