Skip to content
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

Bump go.opentelemetry.io/collector/config/configgrpc from 0.80.0 to 0.102.1 #12

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jun 5, 2024

Bumps go.opentelemetry.io/collector/config/configgrpc from 0.80.0 to 0.102.1.

Release notes

Sourced from go.opentelemetry.io/collector/config/configgrpc's releases.

cmd/builder/v0.102.1

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.102.1

v0.102.1

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.102.1

This release addresses CVE-2024-36129 (GHSA-c74f-6mfw-mm4v) fully.

End User Changelog

🧰 Bug fixes 🧰

  • configrpc: Use own compressors for zstd (#10323) Before this change, the zstd compressor we used didn't respect the max message size. This addresses CVE-2024-36129 (GHSA-c74f-6mfw-mm4v) on configgrpc.

cmd/builder/v0.102.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.102.0

cmd/builder/v0.101.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.101.0

cmd/builder/v0.100.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.100.0

cmd/builder/v0.99.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.99.0

cmd/builder/v0.98.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.98.0

cmd/builder/v0.97.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.97.0

cmd/builder/v0.96.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.96.0

v0.96.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.96.0

End User Changelog

🛑 Breaking changes 🛑

  • configgrpc: Remove deprecated GRPCClientSettings, GRPCServerSettings, and ServerConfig.ToListenerContext. (#9616)
  • confighttp: Remove deprecated HTTPClientSettings, NewDefaultHTTPClientSettings, and CORSSettings. (#9625)
  • confignet: Removes deprecated NetAddr and TCPAddr (#9614)

💡 Enhancements 💡

  • configtls: Add include_system_ca_certs_pool to configtls, allowing to load system certs and additional custom certs. (#7774)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/config/configgrpc's changelog.

Changelog

Starting with version v0.83.0, this changelog includes only user-facing changes. If you are looking for developer-facing changes, check out CHANGELOG-API.md.

v1.9.0/v0.102.0

🛑 Breaking changes 🛑

  • envprovider: Restricts Environment Variable names. Environment variable names must now be ASCII only and start with a letter or an underscore, and can only contain underscores, letters, or numbers. (#9531)
  • confighttp: Apply MaxRequestBodySize to the result of a decompressed body (#10289) When using compressed payloads, the Collector would verify only the size of the compressed payload. This change applies the same restriction to the decompressed content. As a security measure, a limit of 20 MiB was added, which makes this a breaking change. For most clients, this shouldn't be a problem, but if you often have payloads that decompress to more than 20 MiB, you might want to either configure your client to send smaller batches (recommended), or increase the limit using the MaxRequestBodySize option.

💡 Enhancements 💡

  • mdatagen: auto-generate utilities to test component telemetry (#19783)
  • mdatagen: support setting an AttributeSet for async instruments (#9674)
  • mdatagen: support using telemetry level in telemetry builder (#10234) This allows components to set the minimum level needed for them to produce telemetry. By default, this is set to configtelemetry.LevelBasic. If the telemetry level is below that minimum level, then the noop meter is used for metrics.
  • mdatagen: add support for bucket boundaries for histograms (#10218)
  • releases: add documentation in how to verify the image signatures using cosign (#9610)

🧰 Bug fixes 🧰

  • batchprocessor: ensure attributes are set on cardinality metadata metric (#9674)
  • batchprocessor: Fixing processor_batch_metadata_cardinality which was broken in v0.101.0 (#10231)
  • batchprocessor: respect telemetry level for all metrics (#10234)
  • exporterhelper: Fix potential deadlocks in BatcherSender shutdown (#10255)

v1.8.0/v0.101.0

💡 Enhancements 💡

  • mdatagen: generate documentation for internal telemetry (#10170)

  • mdatagen: add ability to use metadata.yaml to automatically generate instruments for components (#10054) The telemetry section in metadata.yaml is used to generate instruments for components to measure telemetry about themselves.

  • confmap: Allow Converters to write logs during startup (#10135)

  • otelcol: Enable logging during configuration resolution (#10056)

🧰 Bug fixes 🧰

... (truncated)

Commits

Dependabot compatibility score

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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [go.opentelemetry.io/collector/config/configgrpc](https://github.com/open-telemetry/opentelemetry-collector) from 0.80.0 to 0.102.1.
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-collector@v0.80.0...v0.102.1)

---
updated-dependencies:
- dependency-name: go.opentelemetry.io/collector/config/configgrpc
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jun 5, 2024
Copy link

dryrunsecurity bot commented Jun 5, 2024

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security Status Findings
Configured Codepaths Analyzer 0 findings
Sensitive Files Analyzer 2 findings
Authn/Authz Analyzer 0 findings
AppSec Analyzer 0 findings
Secrets Analyzer 0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

This pull request updates the Go module dependencies for the qualityTrace project, including upgrading the Go toolchain version from go1.21 to go1.22.3 and updating several dependencies to newer versions. The dependency updates often include bug fixes and security improvements, which is generally a positive change from a security perspective. However, it's important to carefully review the changelog and release notes for each dependency to understand the nature of the changes and any potential security implications. Additionally, the update to the Go toolchain version may introduce changes in the underlying runtime and standard library, which could potentially impact the application's behavior or security. It's recommended to thoroughly test the application with the new toolchain version to ensure there are no regressions or unexpected issues.

Files Changed:

  • go.mod: This file has been updated to specify the Go toolchain version as go1.22.3 and include several dependency updates, such as github.com/fsnotify/fsnotify, github.com/golang/protobuf, github.com/google/uuid, github.com/stretchr/testify, go.opentelemetry.io/collector/component, go.opentelemetry.io/otel, and go.uber.org/zap. The pull request also includes temporary replacements for some github.com/orlangure/gnomock dependencies, likely to address a specific issue until the patches can be merged upstream.

Powered by DryRun Security

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants