-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opentelemetry-collector: 0.101.0 -> 0.103.0 #317233
opentelemetry-collector: 0.101.0 -> 0.103.0 #317233
Conversation
6d9466d
to
d42d634
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector/releases. meta.description for opentelemetry-collector is: Vendor-agnostic implementation on how to receive, process and export telemetry data meta.homepage for opentelemetry-collector is: https://github.com/open-telemetry/opentelemetry-collector meta.changelog for opentelemetry-collector is: https://github.com/open-telemetry/opentelemetry-collector/blob/v0.102.1/CHANGELOG.md Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.) Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages. Result of 1 package built:
Maintainer pingscc @uri-canva @06kellyjac for testing. |
d42d634
to
abc9236
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector/releases. meta.description for opentelemetry-collector is: Vendor-agnostic implementation on how to receive, process and export telemetry data meta.homepage for opentelemetry-collector is: https://github.com/open-telemetry/opentelemetry-collector meta.changelog for opentelemetry-collector is: https://github.com/open-telemetry/opentelemetry-collector/blob/v0.103.0/CHANGELOG.md Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.) Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages. Result of 1 package built:
Maintainer pingscc @uri-canva @06kellyjac for testing. |
Flagging as security related, it includes the fix for CVE-2024-36129 |
Successfully created backport PR for |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector/releases.
meta.description for opentelemetry-collector is: A vendor-agnostic implementation on how to receive, process and export telemetry data
meta.homepage for opentelemetry-collector is: https://github.com/open-telemetry/opentelemetry-collector
meta.changelog for opentelemetry-collector is: https://github.com/open-telemetry/opentelemetry-collector/blob/v0.102.0/CHANGELOG.md
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.tests
, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'
run on x86_64-linux 11 package built:
Maintainer pings
cc @uri-canva @06kellyjac for testing.