-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Prepare release v2.14.0 #7820
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
Prepare release v2.14.0 #7820
Conversation
- Updated CHANGELOG.md with release notes - Updated jaeger-ui submodule - Rotated release managers table
|
|
||
| </details> | ||
|
|
||
| v2.14.0 (2026-01-01) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Date mismatch between CHANGELOG and RELEASE.md. The CHANGELOG shows release date as 2026-01-01 but RELEASE.md shows tentative release date as 7 January 2026. These dates must be consistent. If the release occurred on January 1st, RELEASE.md should reflect that date, not January 7th.
| v2.14.0 (2026-01-01) | |
| v2.14.0 (2026-01-07) |
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
| | 2.17.0 | @albertteoh | 1 April 2026 | | ||
| | 2.18.0 | @pavolloffay | 6 May 2026 | | ||
| | 2.19.0 | @joe-elliott | 3 June 2026 | | ||
| | 2.14.0 | @mahadzaryab1 | 7 January 2026 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incorrect version rotation. The release manager rotation moved v2.14.0 to the end of the table, but the version number should be updated to the next version in the cycle (likely v2.20.0) since v2.14.0 is being released. Keeping v2.14.0 in a future releases table after it's already released (per CHANGELOG.md dated 2026-01-01) creates confusion. The rotation should either:
- Remove v2.14.0 entirely if it's released, OR
- Change v2.14.0 to v2.20.0 with an appropriate future date
Additionally, the date 7 January 2026 conflicts with the CHANGELOG.md date of 2026-01-01.
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7820 +/- ##
==========================================
+ Coverage 95.51% 95.53% +0.02%
==========================================
Files 307 307
Lines 15911 15911
==========================================
+ Hits 15197 15201 +4
+ Misses 561 558 -3
+ Partials 153 152 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This PR prepares the release for v2.14.0.
Changes
After this PR is merged, continue with the release process as outlined in the release issue.