operator-registry
operator-registry copied to clipboard
go upgrade to 1.19
Description of the change: Updated Go version to 1.19
Motivation for the change: https://github.com/operator-framework/operator-registry/issues/1007
Reviewer Checklist
- [ ] Implementation matches the proposed design, or proposal is updated to match implementation
- [ ] Sufficient unit test coverage
- [ ] Sufficient end-to-end test coverage
- [ ] Docs updated or added to
/docs
- [ ] Commit messages sensible and descriptive
Hi @jcho02. Thanks for your PR.
I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/ok-to-test
Codecov Report
Merging #1029 (bf3838e) into master (614d6a9) will increase coverage by
0.01%
. The diff coverage isn/a
.
@@ Coverage Diff @@
## master #1029 +/- ##
==========================================
+ Coverage 51.95% 51.96% +0.01%
==========================================
Files 102 102
Lines 9215 9215
==========================================
+ Hits 4788 4789 +1
+ Misses 3514 3513 -1
Partials 913 913
Impacted Files | Coverage Δ | |
---|---|---|
alpha/veneer/semver/semver.go | 60.50% <0.00%> (+0.50%) |
:arrow_up: |
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
[APPROVALNOTIFIER] This PR is APPROVED
Approval requirements bypassed by manually added approval.
This pull-request has been approved by: jcho02, jmrodri
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment