-
Notifications
You must be signed in to change notification settings - Fork 292
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
go 1.20 #1740
go 1.20 #1740
Conversation
I feel like there was some concern with updating golang version too often. Is that right @natalieparellano or @AidanDelaney ? |
cc also @dfreilich I'd be okay with moving to 1.20 at this point as the minor already has 3 patches. |
Go v1.19 was released in pack https://github.com/buildpacks/pack/releases/tag/v0.29.0, so I'm fine with it in this release :) |
We also need to update the |
also need to fix some uses of |
Signed-off-by: Joe Kimmel <jkimmel@vmware.com>
All of our calls to Seed were with current time, so they were intended to produce different pseudo-random sequences on each run. We were never calling Seed with a fixed value to create reproducible sequences of pseudo-random numbers. Therefore it should be safe to just delete the calls. per the docs (https://pkg.go.dev/math/rand@master#Seed): > If Seed is not called, the generator is seeded randomly at program startup. > Prior to Go 1.20, the generator was seeded like Seed(1) at program startup. To force the old behavior, call Seed(1) at program startup. Alternately, set GODEBUG=randautoseed=0 in the environment before making any calls to functions in this package. > Deprecated: As of Go 1.20 there is no reason to call Seed with a random value. Programs that call Seed with a known value to get a specific sequence of results should use New(NewSource(seed)) to obtain a local random generator. Signed-off-by: Joe Kimmel <jkimmel@vmware.com>
thanks @joe-kimmel-vmw. i'm merging this into #1758 |
Summary
upgrades golang version
Documentation
Related
Resolves #___