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

Backport of update go version to 1.19.4 into release/1.14.x #15716

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #15705 to be assessed for backporting due to the inclusion of the label backport/1.14.

The below text is copied from the body of the original PR.


Description

This upgrade go version to go1.19.4


Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core requested review from shore and modrake and removed request for a team December 7, 2022 20:11
@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/update-go-1.19.4/physically-powerful-krill branch from 4659233 to 5825ef7 Compare December 7, 2022 20:11
@github-actions github-actions bot added theme/contributing Additions and enhancements to community contributing materials type/ci Relating to continuous integration (CI) tooling for testing or releases labels Dec 7, 2022
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@hc-github-team-consul-core hc-github-team-consul-core merged commit 334a436 into release/1.14.x Dec 7, 2022
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/update-go-1.19.4/physically-powerful-krill branch December 7, 2022 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/contributing Additions and enhancements to community contributing materials 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.

None yet

3 participants