Skip to content

Conversation

@yurishkuro
Copy link
Member

This PR prepares the release for v2.14.0.

Changes

  • Updated CHANGELOG.md with release notes
  • Updated jaeger-ui submodule to v2.14.0
  • Rotated release managers table in RELEASE.md

After this PR is merged, continue with the release process as outlined in the release issue.

- Updated CHANGELOG.md with release notes
- Updated jaeger-ui submodule
- Rotated release managers table
@yurishkuro yurishkuro added the changelog:skip Trivial change that does not require an entry in CHANGELOG label Jan 2, 2026
@yurishkuro yurishkuro requested a review from a team as a code owner January 2, 2026 00:27
@yurishkuro yurishkuro added the changelog:skip Trivial change that does not require an entry in CHANGELOG label Jan 2, 2026

</details>

v2.14.0 (2026-01-01)
Copy link
Contributor

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.

Suggested change
v2.14.0 (2026-01-01)
v2.14.0 (2026-01-07)

Spotted by Graphite Agent

Fix in Graphite


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 |
Copy link
Contributor

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:

  1. Remove v2.14.0 entirely if it's released, OR
  2. 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

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

@codecov
Copy link

codecov bot commented Jan 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.53%. Comparing base (55f2347) to head (ec23a21).
⚠️ Report is 12 commits behind head on main.

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     
Flag Coverage Δ
badger_v1 9.18% <ø> (ø)
badger_v2 1.93% <ø> (ø)
cassandra-4.x-v1-manual 13.58% <ø> (ø)
cassandra-4.x-v2-auto 1.92% <ø> (ø)
cassandra-4.x-v2-manual 1.92% <ø> (ø)
cassandra-5.x-v1-manual 13.58% <ø> (ø)
cassandra-5.x-v2-auto 1.92% <ø> (ø)
cassandra-5.x-v2-manual 1.92% <ø> (ø)
clickhouse 1.97% <ø> (ø)
elasticsearch-6.x-v1 17.54% <ø> (ø)
elasticsearch-7.x-v1 17.57% <ø> (ø)
elasticsearch-8.x-v1 17.73% <ø> (ø)
elasticsearch-8.x-v2 1.93% <ø> (ø)
elasticsearch-9.x-v2 1.93% <ø> (ø)
grpc_v1 8.84% <ø> (ø)
grpc_v2 1.93% <ø> (ø)
kafka-3.x-v2 1.93% <ø> (ø)
memory_v2 1.93% <ø> (ø)
opensearch-1.x-v1 17.62% <ø> (ø)
opensearch-2.x-v1 17.62% <ø> (ø)
opensearch-2.x-v2 1.93% <ø> (ø)
opensearch-3.x-v2 1.93% <ø> (ø)
query 1.93% <ø> (ø)
tailsampling-processor 0.55% <ø> (ø)
unittests 94.16% <ø> (+0.02%) ⬆️

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.

@yurishkuro yurishkuro closed this Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog:skip Trivial change that does not require an entry in CHANGELOG

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants