Skip to content

PG-2338 Updated PPG latest versions to reflect Q2-2026 minor version …#5400

Open
Naeem-Akhter wants to merge 1 commit into
percona:v3from
Naeem-Akhter:PG-2332
Open

PG-2338 Updated PPG latest versions to reflect Q2-2026 minor version …#5400
Naeem-Akhter wants to merge 1 commit into
percona:v3from
Naeem-Akhter:PG-2332

Conversation

@Naeem-Akhter
Copy link
Copy Markdown
Collaborator

@Naeem-Akhter Naeem-Akhter commented May 21, 2026

…release.

@Naeem-Akhter Naeem-Akhter requested a review from a team as a code owner May 21, 2026 20:21
@Naeem-Akhter Naeem-Akhter requested review from 4nte, JiriCtvrtka, ademidoff and artemgavrilov and removed request for a team May 21, 2026 20:21
@codecov
Copy link
Copy Markdown

codecov Bot commented May 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.22%. Comparing base (138f6e5) to head (c362da5).

Additional details and impacted files
@@           Coverage Diff           @@
##               v3    #5400   +/-   ##
=======================================
  Coverage   43.22%   43.22%           
=======================================
  Files         413      413           
  Lines       42302    42302           
=======================================
+ Hits        18283    18285    +2     
+ Misses      22152    22151    -1     
+ Partials     1867     1866    -1     
Flag Coverage Δ
managed 42.31% <ø> (+<0.01%) ⬆️

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.

🚀 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.

@artemgavrilov
Copy link
Copy Markdown
Contributor

As for me this check has no sense since it's bundled with PMM

@Naeem-Akhter
Copy link
Copy Markdown
Collaborator Author

Naeem-Akhter commented May 22, 2026

As for me this check has no sense since it's bundled with PMM
@artemgavrilov
I am not aware of whether this check is used in PMM. However, this is what I have been asked to do for the last 2 years or so to update this file for each Major or minor release. Earlier, it was done in the CHECKED repo, which has been archived. Since then, IIRC, @ademidoff asked me to update here moving forward. Maybe he can confirm whether this is needed moving forward.

For background, here is the initial ticket where it started: https://perconadev.atlassian.net/browse/PMM-12010

@ademidoff
Copy link
Copy Markdown
Member

As for me this check has no sense since it's bundled with PMM

Do you mean it makes no sense because once PMM is deployed, the version values will not be updated?

What about users who regularly upgrade their PMM instances? They would still benefit from it, no?

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.

3 participants