Bump go.opentelemetry.io/collector/featuregate from 1.11.0 to 1.14.1

[dependabot[bot]]

Bumps go.opentelemetry.io/collector/featuregate from 1.11.0 to 1.14.1.

Release notes

Sourced from go.opentelemetry.io/collector/featuregate's releases.

v1.14.1/v0.108.1

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

End User Changelog

🧰 Bug fixes 🧰

• mdatagen: Fix a missing import in the generated test file (#10969)

v1.14.0/v0.108.0

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

End User Changelog

🛑 Breaking changes 🛑

• all: Added support for go1.23, bumped the minimum version to 1.22 (#10869)
• otelcol: Remove deprecated ConfmapProvider interface. (#10934)
• confmap: Mark confmap.strictlyTypedInput as stable (#10552)

💡 Enhancements 💡

• exporter/otlp: Add batching option to otlp exporter (#8122)
• builder: Add a --skip-new-go-module flag to skip creating a module in the output directory. (#9252)
• component: Add TelemetrySettings.LeveledMeterProvider func to replace MetricsLevel in the near future (#10931)
• mdatagen: Add LeveledMeter method to mdatagen (#10933)
• service: Adds level configuration option to service::telemetry::trace to allow users to disable the default TracerProvider (#10892) This replaces the feature gate service.noopTracerProvider introduced in v0.107.0
• componentstatus: Add new Reporter interface to define how to report a status via a component.Host implementation (#10852)
• mdatagen: support using a different github project in mdatagen README issues list (#10484)
• mdatagen: Updates mdatagen's usage to output a complete command line example, including the metadata.yaml file. (#10886)
• extension: Add ModuleInfo to extension.Settings to allow extensions to access component go module information. (#10876)
• confmap: Mark module as stable (#9379)

🧰 Bug fixes 🧰

• batchprocessor: Update units for internal telemetry (#10652)
• confmap: Fix bug where an unset env var used with a non-string field resulted in a panic (#10950)
• service: Fix memory leaks during service package shutdown (#9165)
• mdatagen: Update generated telemetry template to only include context import when there are async metrics. (#10883)
• mdatagen: Fixed bug in which setting SkipLifecycle & SkipShutdown to true would result in a generated file with an unused import confmaptest (#10866)
• confmap: Use string representation for field types where all primitive types are strings. (#10937)
• otelcol: Preserve internal representation when unmarshaling component configs (#10552)

API Changes

🛑 Breaking changes 🛑

• extensions: Remove StatusWatcher interface. Use componentstatus.Watcher instead. (#10777)
• component: Removed Status related types and functions. Use componentstatus instead. (#10777)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/featuregate's changelog.

v1.14.1/v0.108.1

v1.14.0/v0.108.0

🛑 Breaking changes 🛑

• extensions: Remove StatusWatcher interface. Use componentstatus.Watcher instead. (#10777)
• component: Removed Status related types and functions. Use componentstatus instead. (#10777)
• component: Remove ReportStatus from TelemetrySettings. Use componentstatus.ReportStatus instead. (#10777)
• componentstatus: Make componentstatus.InstanceID immutable. (#10494)

🚩 Deprecations 🚩

• scraperhelper: deprecate NewObsReport, ObsReport, ObsReportSettings, scrapers should use NewScraperControllerReceiver (#10959)
• mdatagen: Deprecating generated Meter func in favour of LeveledMeter (#10939)
• connector: Deprecate connector.Builder, and move it into an internal package of the service module (#10784)
• exporter: Deprecate exporter.Builder, and move it into an internal package of the service module (#10783)
• extension: Deprecate extension.Builder, and move it into an internal package of the service module (#10785)
• processor: Deprecate processor.Builder, and move it into an internal package of the service module (#10782)
• receiver: Deprecate receiver.Builder, and move it into an internal package of the service module (#10781)

v1.13.0/v0.107.0

🛑 Breaking changes 🛑

• otelcol: Delete deprecated NewCommandMustSetProvider (#10778)
• component: Removes the deprecated Host.GetFactory method. (#10771)
• otelcoltest: The otelcol.LoadConfig method no longer sets the expandconverter. (#10510)
• ocb: Collectors built with OCB will no longer include the expandconverter (#10510)
• exporterhelper: Delete deprecated exporterhelper.ObsReport and exporterhelper.NewObsReport (#10779, #10592)

🚩 Deprecations 🚩

• expandconverter: Deprecate expandconverter. (#10510)

🚀 New components 🚀

• componentstatus: Adds new componentstatus module that will soon replace status content in component. (#10730)
• connector/connectorprofiles: Allow handling profiles in connector. (#10703)
• exporter/exporterprofiles: Allow handling profiles in exporter. (#10702)
• processor/processorprofiles: Allow handling profiles in processor. (#10691)
• receiver/receiverprofiles: Allow handling profiles in receiver. (#10690)

💡 Enhancements 💡

• confmap: Check that providers have a correct scheme when building a confmap.Resolver. (#10786)
• confighttp: Add NewDefaultCORSConfig function to initialize the default confighttp.CORSConfig (#9655)

v0.106.0

... (truncated)

Commits

• c8a932e [chore] Prepare release v1.14.1/v0.108.1 (#10986)
• 1015551 [chore] Prepare release v1.14.0/v0.108.0 (#10980)
• 79bef21 Revert "[builder] Support for --skip-new-go-module (#10098)" (#10978)
• 5963d44 [mdatagen] fix a missing import in a generated test file (#10970)
• 9e1af01 chore(deps): update github/codeql-action action to v3.26.5 (#10967)
• fbdbd50 [scraperhelper] deprecate NewObsReport, ObsReport, ObsReportSettings (#10959)
• 93ecf69 [otelcol] Fix grpclogger to capture correct caller location (#10773)
• 00c8ea9 fix(renovate): add package rule for disabling toolchain updates (#10961)
• bca56c4 [confmaptest] Add a test on empty slice to nil (#10966)
• a80ce1a [chore] Try fixing flaky SharedInstance e2e test (#10929)
• Additional commits viewable in compare view

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)

[pr-commenter[bot]]

Regression Detector

Regression Detector Results

Run ID: 5c58b461-a25a-491d-959b-be63f53a3f6c Metrics dashboard Target profiles

Baseline: f842c1c56f687d046d0be01831087fc99ca04304 Comparison: aa03a4a3e049d40b027d3d67fb39333786832742

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	idle	memory utilization	+0.66	[+0.60, +0.72]	1	Logs
➖	file_tree	memory utilization	+0.42	[+0.29, +0.56]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	+0.30	[-2.22, +2.83]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.25	[+0.20, +0.30]	1	Logs
➖	basic_py_check	% cpu utilization	+0.22	[-2.45, +2.90]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.07	[-0.68, +0.82]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.07, +0.11]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	idle_all_features	memory utilization	-0.14	[-0.26, -0.02]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.89	[-1.70, -0.09]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
✅	idle	memory_usage	10/10

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.