Skip to content
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

Merged
merged 7 commits into from
Oct 24, 2022
Merged

Update go version to 1.19 #15090

merged 7 commits into from
Oct 24, 2022

Conversation

kisunji
Copy link
Contributor

@kisunji kisunji commented Oct 21, 2022

Upgrading the go version to 1.19

Highly recommended to review by commit.

Includes:

  • General CI/CD version bumps
  • Changelog
  • go1.19-style gofmt

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

@github-actions github-actions bot added pr/dependencies PR specifically updates dependencies of project type/ci Relating to continuous integration (CI) tooling for testing or releases labels Oct 21, 2022
@kisunji kisunji requested a review from a team October 21, 2022 14:35
@kisunji kisunji added the pr/no-changelog PR does not need a corresponding .changelog entry label Oct 21, 2022
Copy link
Contributor

@DanStough DanStough left a 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

@kisunji
Copy link
Contributor Author

kisunji commented Oct 21, 2022

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 🤔

@kisunji kisunji requested a review from a team October 21, 2022 15:39
@kisunji kisunji requested a review from a team as a code owner October 21, 2022 15:39
@kisunji kisunji requested review from smacfarlane and jeanneryan and removed request for a team October 21, 2022 15:39
@david-yu
Copy link
Contributor

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

@kisunji kisunji removed the pr/no-changelog PR does not need a corresponding .changelog entry label Oct 21, 2022
@kisunji
Copy link
Contributor Author

kisunji commented Oct 21, 2022

1.19 formatting 😭

@kisunji kisunji force-pushed the kisunji/go1.19 branch 3 times, most recently from e78711a to 6d6ceaf Compare October 24, 2022 14:42
@kisunji kisunji closed this Oct 24, 2022
@kisunji kisunji reopened this Oct 24, 2022
@kisunji kisunji force-pushed the kisunji/go1.19 branch 2 times, most recently from 467c945 to 90fe897 Compare October 24, 2022 16:07
@@ -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)
Copy link
Contributor Author

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

@kisunji kisunji force-pushed the kisunji/go1.19 branch 2 times, most recently from e6abf2f to f107d29 Compare October 24, 2022 17:44
@kisunji kisunji requested a review from DanStough October 24, 2022 18:03
@rboyer rboyer dismissed DanStough’s stale review October 24, 2022 19:14

changes were completed

Chris S. Kim added 5 commits October 24, 2022 15:29
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/dependencies PR specifically updates dependencies of project type/ci Relating to continuous integration (CI) tooling for testing or releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants