Skip to content

[release-23.0] ci: use the newest mysql apt config package (#18790)#18794

Merged
frouioui merged 1 commit intorelease-23.0from
backport-18790-to-release-23.0
Oct 23, 2025
Merged

[release-23.0] ci: use the newest mysql apt config package (#18790)#18794
frouioui merged 1 commit intorelease-23.0from
backport-18790-to-release-23.0

Conversation

@vitess-bot
Copy link
Contributor

@vitess-bot vitess-bot bot commented Oct 23, 2025

Description

This is a backport of #18790

Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
@vitess-bot
Copy link
Contributor Author

vitess-bot bot commented Oct 23, 2025

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot requested a review from arthurschreiber October 23, 2025 21:12
@github-actions github-actions bot added this to the v23.0.0 milestone Oct 23, 2025
@arthurschreiber arthurschreiber enabled auto-merge (squash) October 23, 2025 21:32
@codecov
Copy link

codecov bot commented Oct 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.70%. Comparing base (eab5c0d) to head (a58dc78).
⚠️ Report is 1 commits behind head on release-23.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-23.0   #18794      +/-   ##
================================================
+ Coverage         67.53%   69.70%   +2.16%     
================================================
  Files              1605     1605              
  Lines            263808   214449   -49359     
================================================
- Hits             178164   149480   -28684     
+ Misses            85644    64969   -20675     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@frouioui frouioui disabled auto-merge October 23, 2025 22:54
@frouioui frouioui merged commit 58344e1 into release-23.0 Oct 23, 2025
107 of 114 checks passed
@frouioui frouioui deleted the backport-18790-to-release-23.0 branch October 23, 2025 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants