[chore] Backport 0.120.1 into main#38057
Conversation
…dation (open-telemetry#38018) #### Description During the release process, we noticed a breaking change in the Prometheus receiver caused by open-telemetry#36873. In that PR, I tried adding a fallback scrape protocol by default everytime the PrometheusReceiver was built, but it turned out that config validation happened even before the component was created. And the collector fails startup with invalid configuration This PR moves the addition of scrape protocol to the validation step. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#37902 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
The following commands were run to prepare this release: - make chlog-update VERSION=v0.120.1 - sed -i.bak s/0\.120\.0/0.120.1/g versions.yaml - make multimod-prerelease - make multimod-sync
codeboten
left a comment
There was a problem hiding this comment.
The important piece of this PR is ensuring that the first 2 commits make it into main without being squashed, i've enabled merge commits for the repo.
Please make sure to use it once CI has completed
|
The same test is failing on main https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/13415755416/job/37476233796?pr=38057 cc @ArthurSens |
|
This is weird, the test was removed in the previous PR 🤔 |
|
seems a bad merge: the merge commit does not contain these diffs https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/38018/files#diff-8d0532921a098f2bf8b280acabe5c8efe6e320f38ccb8b61b2ca28d54377b033L67-L83 |
|
I'm closing this and check what's wrong later. |
Description
Link to tracking issue
Fixes
Testing
Documentation