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 Pipeline Updates into release/1.1.x #1923

Conversation

thisisnotashwin
Copy link
Contributor

Backport

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

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

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


If you go through my PR commit by commit it's easier to review, I typically add extra context and you won't see things change between commits unintentionally

Changes proposed in this PR:

  • Upgrade Go version to 1.20 and specifically 1.20.1 to address a CVE
  • Updated gotestsum calls to use testnames this improves debugging as you'll see which tests pass and fail, not just the package name with failing/passing tests
  • Added 1.1.x release branch for nightly testing

How I've tested this PR:
I verified that the nightly tests passed:
image

How I expect reviewers to test this PR:
👀

Checklist:

  • [N/A] Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)


Overview of commits

@thisisnotashwin thisisnotashwin force-pushed the backport/mw/fix-pipeline-feb-2023/vastly-smooth-ghost branch from f1a9d14 to cc90754 Compare February 17, 2023 19:30
@wilkermichael
Copy link
Contributor

Closing I'm going to manually cherry-pick

@wilkermichael wilkermichael deleted the backport/mw/fix-pipeline-feb-2023/vastly-smooth-ghost branch March 9, 2023 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants