fix: fix versionCross error #314
Conversation
Signed-off-by: moweiwei <mo.weiwei@99cloud.net>
|
@moweiwei: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
kubeclipper-bot
added
dco-signoff: yes
do-not-merge/release-note-label-needed
approved
|
cherrypick-master |
|
/lgtm |
|
LGTM label has been added. Git tree hash: 0dc4a87f866d6e25995b3a380b8c7420343a3e3c
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lysign, moweiwei The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherrypick master |
|
@moweiwei: once the present PR merges, I will cherry-pick it on top of master in a new PR and assign it to you. In response to this:
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. |
Codecov Report
@@ Coverage Diff @@
## release-1.3 #314 +/- ##
===============================================
+ Coverage 46.20% 47.35% +1.15%
===============================================
Files 7 7
Lines 606 606
Branches 171 171
===============================================
+ Hits 280 287 +7
+ Misses 252 246 -6
+ Partials 74 73 -1
|
|
@moweiwei: new pull request created: #315 In response to this:
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. |
Signed-off-by: moweiwei mo.weiwei@99cloud.net
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: