Skip to content

Conversation

@dmathieu
Copy link
Member

@dmathieu dmathieu commented Dec 3, 2025

The release tracking issue is a bit misleading, as not all actions are actually performed by the collector release manager.
And some actions don't really reflect the release docs.

This splits the core/contrib/releases releases per their respective managers.

I've also updated the "like" issue to a more recent one.

@dmathieu dmathieu marked this pull request as ready for review December 3, 2025 08:57
@dmathieu dmathieu requested a review from a team as a code owner December 3, 2025 08:57
@codspeed-hq
Copy link

codspeed-hq bot commented Dec 3, 2025

CodSpeed Performance Report

Merging #14250 will improve performances by 40.88%

Comparing dmathieu:update-release-tracking-issue (fb281d8) with main (a330ae2)

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

⚡ 8 improvements
✅ 51 untouched
⏩ 20 skipped1

Benchmarks breakdown

Benchmark BASE HEAD Change
BenchmarkTraceSizeSpanCount 60 ns 46 ns +30.43%
BenchmarkLogsToProto2k 63.3 µs 44.9 µs +40.88%
with_a_duplicate_value 60 ns 45 ns +33.33%
with_an_existing_value 60 ns 45 ns +33.33%
BenchmarkProfilesToProto 1.6 µs 1.3 µs +28.76%
BenchmarkTraceSizeBytes 422.1 µs 307.5 µs +37.25%
BenchmarkTracesToProto2k 96 µs 69.3 µs +38.39%
with_a_new_value 60 ns 45 ns +33.33%

Footnotes

  1. 20 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@dmathieu dmathieu added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Dec 3, 2025
@codecov
Copy link

codecov bot commented Dec 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.16%. Comparing base (a330ae2) to head (fb281d8).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #14250   +/-   ##
=======================================
  Coverage   92.16%   92.16%           
=======================================
  Files         668      668           
  Lines       41470    41470           
=======================================
  Hits        38219    38219           
  Misses       2217     2217           
  Partials     1034     1034           

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

Comment on lines 34 to 35
- [ ] Prepare container images release v${CANDIDATE_BETA}
- [ ] Tag and container images release v${CANDIDATE_BETA}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this new wording a bit confusing. Maybe we should standardize on "otelcol" / "otelcol-contrib" / "otelcol-releases" and "Prepare X release Y" / "Tag and release X vY"?

Copy link
Member Author

@dmathieu dmathieu Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree finding a good name is tricky here. I can switch to otelcol though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip Changelog PRs that do not require a CHANGELOG.md entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants