[chore] v0.131.0 Changelog

[dloucasfx]

Description:

Link to Splunk idea: <Link to Splunk idea, see https://ideas.splunk.com>

Testing:

Documentation:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.04%. Comparing base (4831a1f) to head (4322764).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6515      +/-   ##
==========================================
+ Coverage   44.03%   44.04%   +0.01%     
==========================================
  Files         376      376              
  Lines       26459    26459              
==========================================
+ Hits        11650    11653       +3     
+ Misses      13980    13978       -2     
+ Partials      829      828       -1     

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

[pjanotti]

I don't think this directly matters to our users.

Same for the line below.

[pjanotti]

More generally we try to list changes not directly visible to our users, so API and internal changes are typically not included.

[dloucasfx]

I was not aware that this is the approach we follow.
Back in SWAT, we used to look at the changelog when run into bugs related to internal components, I think it's very useful and speed up the process of not looking at code

[pjanotti]

hum but it is not what we have been doing, I'm fine as long as we start to do it consistently. It does simplify the process on our side.

[pjanotti]

anyway, my intention is similar to #6515 (comment)

so I guess we are still trying to remove some of those, the Q is that there is always a bit of judgement here

[hughesjj]

I figure the customers could always skim past it if not. Personally, if I'm looking through change logs I'd want to know all the context that changed and not less.

I'd imagine the intended audience for these Changelogs are other developers and not, like, product. Even if it is product, I'd imagine they're just searching for anything which piques their interest, and they can just skim over this line, because they see it marked as pdata and thus wouldn't care about it

[jinja2]

does this change (continuousDiscovery one) have any implication for a user upgrading? i think there was some discussion about disallowing customized rules? is that the breaking change?

[dloucasfx]

@dmitryax ?

[dloucasfx]

In the latest push, I have added the upstream changelogs links

This Splunk OpenTelemetry Collector release includes changes from the [opentelemetry-collector v0.131.0](https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.131.0)
and the [opentelemetry-collector-contrib v0.131.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.131.0) releases where appropriate.