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

[release-1.31] Bump canal to v3.28.1-build20240830 #6687

Conversation

mgfritch
Copy link
Contributor

@mgfritch mgfritch commented Sep 2, 2024

Issue: #6683
Backport: #6677

Signed-off-by: Michael Fritch <[email protected]>
(cherry picked from commit cee7030)
@mgfritch mgfritch requested a review from a team as a code owner September 2, 2024 19:32
@codecov-commenter
Copy link

codecov-commenter commented Sep 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.18%. Comparing base (3acd10e) to head (4a40259).

Additional details and impacted files
@@              Coverage Diff              @@
##           release-1.31    #6687   +/-   ##
=============================================
  Coverage         25.18%   25.18%           
=============================================
  Files                33       33           
  Lines              2831     2831           
=============================================
  Hits                713      713           
  Misses             2071     2071           
  Partials             47       47           
Flag Coverage Δ
inttests 9.57% <ø> (ø)
unittests 17.80% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mgfritch mgfritch merged commit 58e7164 into rancher:release-1.31 Sep 9, 2024
6 checks passed
@mgfritch mgfritch deleted the bump-canal-v3.28.1-build20240830-release-1.31 branch September 9, 2024 16:55
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.

4 participants