-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Update go version to 1.19 #15090
Update go version to 1.19 #15090
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was taking a look at https://github.com/hashicorp/consul/pull/12808/files for reference, and I see a few more places to change:
- .github/workflows/build.yaml
- build-support/docker/Build-Go.dockerfile
- (new) test/integration/consul-container/go.mod
TBH I'm not really sure if we do changelogs for these changes, so maybe it's not necessary
Thanks for catching these! I grepped for 1.18 but those didn't come up for some reason 🤔 |
e3696c9
to
fa5f665
Compare
We typically do include changelog details as its helpful to know when go was updated https://github.com/hashicorp/consul/blob/main/CHANGELOG.md#1120-april-20-2022 |
c555f06
to
aa76dff
Compare
1.19 formatting 😭 |
e78711a
to
6d6ceaf
Compare
467c945
to
90fe897
Compare
@@ -6,5 +6,5 @@ export GIT_DIRTY=$(test -n "`git status --porcelain`" && echo "+CHANGES" || true | |||
export GIT_IMPORT=github.com/hashicorp/consul/version | |||
# we're using this for build date because it's stable across platform builds | |||
# the env -i and -noprofile are used to ensure we don't try to recursively call this profile when starting bash | |||
export GIT_DATE=$(env -i /bin/bash --noprofile -norc ${CIRCLE_WORKING_DIRECTORY}/build-support/scripts/build-date.sh) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was not expanding correctly: https://discuss.circleci.com/t/circle-working-directory-doesnt-expand/17007
this caused all CI runs to output:
~/project/build-support/scripts/build-date.sh: No such file or directory
90fe897
to
001fcd4
Compare
e6abf2f
to
f107d29
Compare
These tests started failing in go1.19, presumably due to support for valid 1xx responses being added. golang/go#56346
The service was never successfully running and did not fail any tests
061b973
to
faec56c
Compare
Upgrading the go version to 1.19
Highly recommended to review by commit.
Includes:
Note:
The linter
unparam
has not been active in go1.18 due to a bug. This resulted in several features developed recently (peering) to fail the linter in minor ways (unused return variable). I've added TODO's in those files to clean them up