You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of hard-coding a version of go and having to change that every few months when the versions of golang update.
I don't see a reason not to use stable. We want the buildpacks to be built with the latest stable; we don't need to validate that the buildpacks are able to be built with older versions of golang.
For libraries (e.g. packit, libnodejs, etc), we could expand this to a matrix support, consisting of stable and oldstable if we wanted to validate that the libraries still work fine on all supported versions of golang.
The text was updated successfully, but these errors were encountered:
According to the setup-go action documentation, we can use:
Instead of hard-coding a version of go and having to change that every few months when the versions of golang update.
I don't see a reason not to use
stable
. We want the buildpacks to be built with the latest stable; we don't need to validate that the buildpacks are able to be built with older versions of golang.For libraries (e.g. packit, libnodejs, etc), we could expand this to a matrix support, consisting of
stable
andoldstable
if we wanted to validate that the libraries still work fine on all supported versions of golang.The text was updated successfully, but these errors were encountered: