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
For whatever reasons there is a versionsMap in the go-helpers.ts.
This map indicates what Go versions are supported by Vercel.
As of today, this map will be updated by the community from time to time.
See also #11572 #11156 #10552 #9576 #7590 #7002
... And probably more 🙃
Does it make sense to introduce some automation (GitHub Action) that runs periodically, checks for Go updates and adjust the map automatically? 🤔
We could also start by introducing this only for patch versions.
However, Go is known to not breaking stuff for minot releases. So I woulnd't see the point.
Maybe, as another idea, supporting "any patch" and getting rid of the map in terms of "maximum version" would probably also a good idea?! 🤔
What do you think?
The text was updated successfully, but these errors were encountered:
For whatever reasons there is a
versionsMap
in thego-helpers.ts
.This map indicates what Go versions are supported by Vercel.
As of today, this map will be updated by the community from time to time.
See also
#11572
#11156
#10552
#9576
#7590
#7002
... And probably more 🙃
Does it make sense to introduce some automation (GitHub Action) that runs periodically, checks for Go updates and adjust the map automatically? 🤔
We could also start by introducing this only for patch versions.
However, Go is known to not breaking stuff for minot releases. So I woulnd't see the point.
Maybe, as another idea, supporting "any patch" and getting rid of the map in terms of "maximum version" would probably also a good idea?! 🤔
What do you think?
The text was updated successfully, but these errors were encountered: