-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Build current and next Go version #1163
base: master
Are you sure you want to change the base?
Conversation
8be1b63
to
197aa6d
Compare
7ec599c
to
6cf50ff
Compare
What do you think about just supporting |
@dm-2 that's a good point I didn't think of - if someone had a problem on older golang we'd just tell them to use "current". I'll make that change 👍
|
CI is exploding at:
I wonder if this is a golang 1.18 problem 🤔 |
I've noticed this error on a couple of other PRs today, re-running CI was successful - I haven't dug into why! |
Oh ok, in that case it's not a go 1.18 problem as this PR isn't merged 🤔 EDIT: misread the output. We print-out a golang stack on test errors, I misread this as a panic |
Signed-off-by: Tim Vaillancourt <[email protected]>
Description
This PR updates to Golang 1.20 and concurrently tests that
gh-ost
builds on the following golang versions:Only the "current" job uploads the binary artifact due to an expression
Example in Actions (notice upload is skipped because 1.21 is not the current version):
TBD
Also, many Actions were updated to recent major versions without issue. TIL
action/setup-go
supportsgo-version-file: go.mod
to read the version fromgo.mod
vs duplicating 🎉script/cibuild
returns with no formatting errors, build errors or unit test errors.