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

Add go1.23.1 and go1.22.7 as new defaults #573

Merged
merged 2 commits into from
Sep 5, 2024
Merged

Add go1.23.1 and go1.22.7 as new defaults #573

merged 2 commits into from
Sep 5, 2024

Conversation

joshwlewis
Copy link
Member

@joshwlewis joshwlewis commented Sep 5, 2024

New go releases are available as of 2024-09-05.

  • Add go1.23.1
  • Add go1.22.7
  • go1.23 defaults to 1.23.1
  • go1.22 defaults to 1.22.7

@joshwlewis joshwlewis requested a review from a team as a code owner September 5, 2024 16:38
@joshwlewis joshwlewis enabled auto-merge (squash) September 5, 2024 16:49
@joshwlewis joshwlewis merged commit 89f62b2 into main Sep 5, 2024
5 checks passed
@joshwlewis joshwlewis deleted the jwl/go1.23.1 branch September 5, 2024 16:59
@brandur
Copy link

brandur commented Sep 9, 2024

@joshwlewis Hey, is it possible this change needs a deploy (or something like that)? We're getting this error trying to push 1.23.1:

remote: -----> New Go Version, clearing old cache
remote: -----> Installing go1.23.1
remote:  !!
remote:  !!    The requested file (go1.23.1.linux-amd64.tar.gz) is unknown to the buildpack!
remote:  !!
remote:  !!    The buildpack tracks and validates the SHA256 sums of the files
remote:  !!    it uses. Because the buildpack doesn't know about the file
remote:  !!    it likely won't be able to obtain a copy and validate the SHA.
remote:  !!
remote:  !!    To find out more info about this error please visit:
remote:  !!        https://devcenter.heroku.com/articles/unknown-go-buildack-files
remote:  !!
remote:  !     Push rejected, failed to compile Go app.
remote:
remote:  !     Push failed

@joshwlewis
Copy link
Member Author

My apologies -- this release (v197) wasn't tagged in the buildpack registry. It is now.

@brandur
Copy link

brandur commented Sep 9, 2024

Great — thank you. I just tried again and it's working now!

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.

3 participants