Release v0.16.0

[jade-guiton-dd]

v0.16.0

🚀 New components 🚀

• githubgen: Moved githubgen tool here from open-telemetry/opentelemetry-collector-contrib (feat: add githubgen tool #639)

💡 Enhancements 💡

• crosslink: Adds a 'tidy' subcommand to generate 'go mod tidy' schedules (Add crosslink tidylist command #642)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 48.86%. Comparing base (3f22feb) to head (ebdd377).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #656   +/-   ##
=======================================
  Coverage   48.86%   48.86%           
=======================================
  Files          57       57           
  Lines        3381     3381           
=======================================
  Hits         1652     1652           
  Misses       1568     1568           
  Partials      161      161           

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

[MrAlias]

There is follow up underway to this new component: #655

This release seems premature.

[mx-psi]

@MrAlias I think @jade-guiton-dd is interested in releasing #642, not the githubgen changes. I guess we could temporarily revert #639, do the release, then apply #639 again?

[mowies]

It should be fine to release even with githubgen. the tool works as is for open-telemetry/opentelemetry-collector-contrib, just not for other use cases. That's what the follow up PR is for.
Either way, the tool is not used anywhere as a dependency yet, so it should be fine as is as well.

[jade-guiton-dd]

Yes, I was hesitating to do a release because of the follow up PR. It sounds like it should be okay, but we can delay the release if you feel it necessary. I could use a pseudo-version on contrib in the meantime to start integrating #642.

[MrAlias]

I feel we need to revert prior to a release given approvals for #639 were made with the assumption that things would be fixed.

[dmathieu]

Couldn't we just remove it from versions.yaml so it's not released rather than a full revert?

[jade-guiton-dd]

@dmathieu I can try doing a partial release with only crosslink. Has that been done before?

[dmathieu]

I believe that would require doing the release manually, which doesn't look like a good idea.

[jade-guiton-dd]

I'll try the release again excluding just githubgen.