Closed ashmckenzie closed 6 months ago
Yeah, it makes sense to update this. We really should be defaulting to a version that is actually supported by the go team. I just added go1.20.14 in #544. Mind updating to that? This will also need a CHANGELOG.md entry.
~It's a shame my commit wasn't cherry picked into https://github.com/heroku/heroku-buildpack-go/pull/544 and then updated to 1.20.14 but I guess as long as the bug is fixed.~
~Closing now that https://github.com/heroku/heroku-buildpack-go/pull/544 is merged.~
Apologies for the misunderstanding, re-opening.
@ashmckenzie thanks for the update / rebase. This is looking like a breaking change (for folks still using old go versions and/or old module management systems), so I'm proceeding cautiously. I've fixed a few broken tests, I'll continue to address the rest.
I haven't decided if this can be merged just yet. There might need to be some deprecation messaging first.
Thanks for the update @joshwlewis 🙇 Is it too late to move to semantic versioning for the tags and make this a major change? (I know the answer 🙂)
@ashmckenzie thanks again. I am going to bring this in to main, but wait to ship it until next week.
I noticed when trying to deploy a Go app via dokku using Go version
devel-a10e42f
(which is is https://github.com/golang/go/releases/tag/go1.22.0) I received the following error using the most recent https://github.com/heroku/heroku-buildpack-go/ (0210495):Before
After
Increasing
DefaultVersion
togo1.20.13
as recommended then allows custom Go versions to be built.