Bump github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor from 0.103.0 to 0.116.0 #1476
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor from 0.103.0 to 0.116.0.
Release notes
Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor's releases.
... (truncated)
Changelog
Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor's changelog.
... (truncated)
Commits
2839359
[chore] Prepare release 0.116.0 (#36864)defc07b
chore: [receiver/hostmetrics] Fix integration tests (#36847)36945ee
[chore] Prepare release v0.116.0 (#36863)1a43701
[chore] switch to ubuntu 24.04 to identify breaking changes (#36839)ddfadc2
[opampsupervisor] avoid nil pointer access when reporting remote config statu...1f10e2d
Trigger windows e2e tests when windows-related files change (#36857)43d345e
[extension/sumologic] Skip zombie processes on Windows (#36772)8be3693
[chore] make update-otel (#36851)d1135ca
[jaegerreceiver] Remove ineffectual warning log (#36831)a8821cd
[chore] make update-otel should commit tidy changes (#36855)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)