Repository navigation
fix(deps): update all updates - #1820
red-hat-konflux[bot] wants to merge 1 commit into
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: 🔵 Low · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title identifies dependency updates, which are the main change, but “update all updates” is redundant and does not identify the scope clearly. |
| Description check | ✅ Passed | The description gives a detailed list of dependency and image digest updates with release notes. It omits the template’s checklist and Testing Performed section, so test status and any applicable chec… |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches 💡 1
-
🛠️ Fix failing CI checks 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
Comment @coderabbitai help to get the list of available commands.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1820 +/- ##
=======================================
Coverage 33.45% 33.45%
=======================================
Files 22 22
Lines 3623 3623
Branches 3623 3623
=======================================
Hits 1212 1212
Misses 2402 2402
Partials 9 9 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
2e31e3a to
cc5ae41
Compare
|
/konflux-retest fact-on-push |
cc5ae41 to
622bc03
Compare
|
/konflux-retest fact-on-push |
622bc03 to
eb0be13
Compare
|
/konflux-retest fact-on-push |
eb0be13 to
c00631e
Compare
|
/konflux-retest fact-on-push |
95c720f to
b0640d7
Compare
7fdc890 to
c52c3ec
Compare
284ce05 to
a703b5e
Compare
6444d03 to
ea6bf2c
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
ea6bf2c to
cf2b267
Compare
|
/konflux-retest fact-on-push |
2 similar comments
|
/konflux-retest fact-on-push |
|
/konflux-retest fact-on-push |
This PR contains the following updates:
1.11.1→1.12.00.1.20→0.1.210.2.189→0.2.1900.2.1910.32.0→0.33.00.32.0→0.33.00.32.1→0.33.00.10.2→0.10.3c5cc9c2→16e9e43c5cc9c2→16e9e437a0454c→5be877a1.0.151→1.0.1542.0.20→2.0.211.26.1→1.28.0Release Notes
hyperium/hyper (hyper)
v1.12.0Compare Source
Bug Fixes
Features
v1.11.1 (2026-08-27)
Bug Fixes
\n\r\nas a head terminator in the partial-read fast path (#4147) (3534d75c, closes #4145)hyperium/hyper-util (hyper-util)
v0.1.21Compare Source
This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.
This release bumps the rust edition from 2021 to 2024.
Additions
client::legacy::Builder::http2_header_table_size()method. (#274)client::legacy::Builder::http2_max_concurrent_streams()method. (#274)client::legacy::Builder::http2_max_local_error_reset_streams()method. (#277)client::legacy::connect::HttpConnector::set_mark()method. (#303)rt::tracing::WithSpanExecutor<E>,hyper_util::rt::tracing::CurrentSpanExecutor<E>, andhyper_util::rt::tracing::MkSpanExecutor<E, F>executors. (#323)Fixes
client::legacy::Clientso that it properly validates CONNECT responses. (#315)client::legacy::Clientto cancel the idle interval once its pool empties. (#292)client::legacy::Clientto properly handle IPv6 addresses when using a SOCKS proxy. (#302)client::pool::cacheto preserve readiness with clones. (#297)client::pool::cacheto wake its waiters in FIFO order. (#298)client::pool::singleton::Singletonto properly handle cancellation. (#299)client::pool::singleton::Singletonto share errors with all waiters. (#296)client::proxy::matcherhandling for IP wildcards. (#309)tokio/netfeature is narrowed to theclient-legacyfeature flag, from theclientfeature flag. (#276)client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)Changes
This release contains a minor behavioral change for users of the
tracingfeature flag to be aware of.
This feature flag was introduced in v0.1.11. When enabled,
rt::TokioExecutor<E>began propagating the currently activetracing::Spanto spawned tasks when
hyper::rt::Executor::execute()is called. This causedissues for some users, due to background tasks keeping a span open for the
duration of a long-lived connection.
This behavior has now been removed from
rt::TokioExecutor<E>(#322) by default. A
collection of executor wrappers have been added to a new
rt::tracingsubmodule, to provide facilities for instrumenting a client or server's spawned
tasks. See the module-level documentation of
rt::tracingfor moreinformation.
To temporarily preserve the previous
rt::TokioExecutor<E>span propagationbehavior, enable the
rt-tracing-exec-forcefeature. Note that this featureflag will be removed in a future release.
rust-lang/libc (libc)
v0.2.190Compare Source
There is now a single config for enabling 64-bit
time_t:libc_unstable_time64. This can be setunconditionally; it opts in to 64-bit
time_ton the following platforms that use 32-bit bydefault:
musl v1.2.
Most other 32-bit platforms are either already using 64-bit
time_t, or are considered legacyand will not be gaining support from their upstream maintainers.
You can enable this using
RUSTFLAGS:RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...Note that there may still be some changes to features gated by this config option, hence "unstable"
in its name. In the near future we will rename it to just
libc_time64. Until then, please test itout and report any bugs you find!
Support
Added
We are slowly filling out the
Defaultimplementations, to reduce the need formem::zeroed()in user code:Defaultfor a number of structs, especially on Apple platforms (#5576)statvfsaDefaultimpl (#5583)Defaultto alinux/can.rsstructs (#5257)Other additions:
libc_unstable_time64cfg (#5411)pthread_gettid_np(#5359)RTLD_NEXT(#5323)NET_RT_DUMP2(#5442)posix_spawn_file_actions_add(f)chdir(_np)(#5558)BPF_WORDALIGN(#5320)lchmodandlchflagswhere supported (#5400)minheritand related constants (#4849)AT_RENAME_*andRENAME_*constants (#5560)renameat2(#5563)rt_msghdrandrt_metrics(#5367)libc_unstable_gnu_time_bits(#5242)environ(#5339)f_typefield tostatvfsandstatvfs64(#5434)STATX_*constants (#5412)SIGEV_THREAD_ID(#5375)*_SUPER_MAGICconstants (#5453)statxalways available (#5448)max_align_t(#5389)BCACHEFS_SUPER_MAGIC(#5516)ETH_P_LLDP(#5438)FUTEX_ROBUST_UNLOCKandFUTEX_ROBUST_LIST32(#5525)NLMSG_*helpers (#5321)siginfo_tand add more getter functions (#5345)SYS_futex_waitv(#5527)__errno(#5346)RTLD_NODELETEandRTLD_NOLOAD(#5377)getexecpath(#5465)sensors.h(#5510)HW_*sysctl constants (#5371)FILENAME_MAX(#5530)clock_settimeandpause(#5363)getrandombindings (#5333)group_req/group_source_reqandMCAST_*where supported (#5236)HOST_NAME_MAX(#5531)_PATH_BSHELLand_PATH_DEFPATHwhere available (#5449)SOCK_CLOEXEC(#5336)time_ton 32-bit platforms via cfg (#5261)Deprecated
_kernel_simple_lock(#5380)*_MIN/*_MAXin favor of e.g.c_int::MAX(#5404)fallocate64, which does not exist on the platform (#5242)glob64types and routines (#5242)syscall,mincore, andKERN_NSELCOLL, all of which have been removed upstream (87992e9895c2)tmpnam,tempnam(#5478)Fixed
BPF_ALIGNMENTtosize_tto match upstream and harmonize with other platforms. (#5373)BPF_ALIGNMENTtosize_tto match upstream and harmonize with other platforms. (#5348)fileops_t.fo_select(#5380)file(#5380)ucontext_t(#5189)O_flags (#5554)mcontext_tanducontext_tand make them usable on more platforms (#5127)glob_tandstatvfs(#5127)sigeventand correct the layout of otherpthread.htypes (#5127)sem_t(#5351)statvfs64on 32-bit RISC-V (#5518)ipc_perm(#5527)uc_flagsfield inucontext_t(#5527)WIFSTOPPED(#5458)time_talias. This is a correction on Arm32 RTEMS (#5132)O_open flags (#5414)socket.hdefinitions (#5313)signal.htypes (#5436)Changed
libc_unstable_musl_v1_2_3has been renamed to a more accuratelibc_unstable_musl_v1_2. The old version will continue to work for now, but will be removed in1-2 releases. (#5376)
unsafe(#5380)POSIX_SPAWN_*flags toc_short(#5572)FD_*functions (#5528)__riscv_mc_q_ext_state.__reservedand make it private (#5533)statfields non-pub(#5542)Removed
libcexposed quite a bit of API on all Apple platforms that is not actually available anywhere other than MacOS. This release removes a number of these cases.mach.hAPI on Apple mobile OSs (e6bfb187513c)exec*andforkcalls from tvOS and watchOS (#5158)Additionally, this release cleans up a lot of API that has been deprecated since at least libc 0.2.100, released 2021-08-20.
af_alg_ivtrait implementations. The have been deprecated for a long time because they allowed out-of-bounds reads via safe functions. (444db4456f38)Other removed items:
INHERIT_ZEROthat does not exist upstream (#5587)REG_*definitions (#5527)REG_NARGS(#5527)A huge thank you to our GSoC student Adam Martinez (@dybucc) who did a
huge amount of the time64 work, as well as many of the platform fixes!
open-telemetry/opentelemetry-rust (opentelemetry)
v0.33.1Compare Source
Released 2026-Oct-08
Context::with_value()callsContext::current()from itsDropimplementation.(#828).
CallbackandAsyncInstrumentBuilder::with_callback).(#3640)
TraceState::from_strrejecting valid optional whitespace around list members.(#3757)
v0.33.0Compare Source
Released 2026-Sep-18
TraceStateaccepting more than the 32 list-members the W3C trace-contextspecification allows.
from_str,from_key_valueandinsertnow keep at most32, dropping members from the end of the list as the specification prescribes, so
neither a parsed nor a locally built
tracestatecan exceed the limit.ContextObservercan be registered viaGlobalContextObserver::setto benotified of context transitions through the
on_context_enterandon_context_exitcallbacks. This feature is primarily intended to publish adifferent view of the current context (the
ObserverContextView) throughalternative channels that let external readers (e.g. an eBPF profiler) track
the current context. See the associated
OTEP.
Gated behind the
experimental_context_observerfeature flag.otel_info!,otel_warn!,otel_debug!, andotel_error!macros now accept quoted-key fields(e.g.
"otel.component.type" = "value") for dotted attribute names.BoundGauge<T>andBoundUpDownCounter<T>types (and thecorresponding
Gauge::bind()/UpDownCounter::bind()methods), completingthe experimental bound-instrument API across all sync instruments
(
Counter,UpDownCounter,Histogram,Gauge). Gated behind theexperimental_metrics_bound_instrumentsfeature flag.open-telemetry/opentelemetry-rust (opentelemetry-otlp)
v0.33.1Compare Source
Released 2026-Oct-08
opentelemetry-proto.v0.33.0Compare Source
Released 2026-Sep-18
Exporter builder usage and environment configuration are unchanged.
Breaking for callers parsing compression strings:
Compression::from_str(including
.parse::<Compression>()) now returns the opaqueParseConfigErrorinstead of
ExporterBuildError. Update explicit result types and error handlingthat expects
ExporterBuildError::UnsupportedCompressionAlgorithm. The new errorimplements
Displayandstd::error::Error; its message is for diagnostics.Accepted strings and parsing behavior are unchanged.
Interpret protocol, compression, and metrics temporality environment values
case-insensitively. Treat empty values as unset, and warn and ignore invalid,
non-Unicode, or feature-unavailable enum values so resolution can continue
to the next environment variable or default. Compression
noneexplicitlydisables compression, including when a generic compression value is set.
Programmatic configuration remains strict.
Retry
policy uses exponential backoff and jitter with up to 3 retries (4 attempts
total). Use
.with_retry_policy(RetryPolicy::disabled())to disable retries,or provide a custom
RetryPolicyto change the behavior.Cargo.tomlenablesexperimental-grpc-retryorexperimental-http-retry, remove those feature flags. No migration action isrequired for users who did not enable them.
#3621
retryandretry_classificationmodules crate-private,removing their retry engine, error type, and protocol classifiers from the
public API.
RetryPolicyremains available from the crate root with privatefields and fluent configuration methods. Replace imports from
opentelemetry_otlp::retrywithopentelemetry_otlp::RetryPolicy, and replacestruct literals with its
with_*methods.#3672
Retry fixes
The following fixes apply to retry behavior that was experimental before this
release:
specification. The exporter now also honors
Retry-Afteron 503 responses.RetryInfodelays returned withUnavailableresponses.RetryInfoandRetry-Afterdelays when subsequent export attempts fail.Other changes
Exporter compression configuration and behavior are unchanged; users of
.with_compression(...)need no changes. Breaking only for direct conversioncallers: removed
TryFrom<Compression>fortonic::codec::CompressionEncoding. Code explicitly converting between theseenums must map the variants itself.
Return an exporter build error when construction of a built-in reqwest HTTP
client fails instead of silently falling back to a client without the
exporter-configured timeout. Failure to spawn the blocking client's setup
thread, or a panic in that thread, is also returned instead of panicking.
Breaking Removed
Defaultfrom theTonicExporterBuilderSetandHttpExporterBuilderSettypestate markers. This also removesDefaultfromthe transport-selected exporter builders (e.g.
SpanExporterBuilder<TonicExporterBuilderSet>). Use the intended builderflow instead:
Also removed the unused
#[doc(hidden)]NoExporterConfigtype.Breaking Mark
ProtocolandCompressionas non-exhaustive so new OTLPprotocols, encodings, and compression algorithms can be added without
breaking downstream users. External exhaustive matches must add a wildcard
arm. Constructing existing variants and passing them to exporter builders is
unchanged.
Breaking Make
Protocol::from_env()crate-private. Exporter buildersalready resolve
OTEL_EXPORTER_OTLP_PROTOCOLwhen built; applications thatneed to inspect the raw environment setting should read the variable
directly.
Breaking Remove
OTEL_EXPORTER_OTLP_ENDPOINT_DEFAULT, which always heldthe HTTP default (
http://localhost:4318) despite gRPC usinghttp://localhost:4317. Omit.with_endpoint(...)to let the selectedtransport use its correct default, or provide the appropriate URL explicitly.
#3690
Breaking Restrict
MetricExporterBuilder::with_http()andwith_tonic()to builders where no transport has been selected, matching the span and log
exporter builders. Select a transport once;
with_temporality()remainsavailable before or after transport selection.
Breaking Remove the public
HttpExporterBuilderandTonicExporterBuildertransport-first APIs. Configure transports through thesignal builders instead:
HttpExporterBuilder::default()with the corresponding signalexporter builder followed by
.with_http(), then replace.build_span_exporter()or.build_log_exporter()with.build()..build_metrics_exporter(temporality)with.with_temporality(temporality).build().TonicExporterBuilder::default()with the corresponding signalexporter builder followed by
.with_tonic().Transport-specific configuration methods remain available after
.with_http()or.with_tonic().Breaking Removed the deprecated
tlsfeature alias. Replacetlswithtls-ring, or selecttls-aws-lcortls-provider-agnosticexplicitly.Exporter builder usage is unchanged. Breaking for code matching or constructing
removed error variants: Simplified
ExporterBuildErrorto the exhaustiveInvalidConfiguration(String)andInternalFailure(String)variants.The enum is no longer marked
#[non_exhaustive].Configuration errors such as invalid endpoints, missing HTTP clients,
transport/protocol mismatches, and missing compression features now use
InvalidConfiguration. Replace implementation-specific, non-exhaustivematches such as:
with an exhaustive match over the two stable categories:
Code that propagates build errors with
?without inspecting their variantsneeds no changes.
Tonic endpoint errors identify the originating environment variable when
validating the URI or reporting endpoint-related TLS setup failures.
#3691
Return an exporter build error for invalid OTLP/HTTP endpoint environment
variables instead of silently falling back to another endpoint or localhost.
Empty endpoint environment variables are now treated as unset.
Return an exporter build error for invalid OTLP/gRPC endpoint environment
variables instead of silently falling back to another endpoint or localhost.
Empty endpoint environment variables are now treated as unset.
Add
WithHttpConfig::with_max_request_body_sizeto configure the HTTP requestbody limit. OTLP/HTTP request bodies are now limited to 64 MiB by default, before and
after compression; oversized requests are discarded without being sent or
retried.
Breaking Seal
WithExportConfig,WithHttpConfig, andWithTonicConfig. These traits remain public for calling configurationmethods on OTLP builders, but can no longer be implemented for external
types.
Add support for INSECURE environment variables for gRPC (env-var-only, no builder method, per spec):
OTEL_EXPORTER_OTLP_INSECURE(generic),OTEL_EXPORTER_OTLP_TRACES_INSECURE,OTEL_EXPORTER_OTLP_METRICS_INSECURE,OTEL_EXPORTER_OTLP_LOGS_INSECURE.Per the spec, these only apply to gRPC connections. When an endpoint has no explicit scheme,
INSECURE=trueuseshttp://,INSECURE=false(default) useshttps://with auto-TLS.Breaking: Schemeless endpoints (e.g.,
collector.example.com:4317) now default tohttps://instead of being passed as-is. Set
OTEL_EXPORTER_OTLP_INSECURE=truefor plaintext connections.Endpoints with an explicit scheme (e.g.,
http://,https://,unix://) are unaffected.#774
#984
Breaking Removed the
serializefeature flag and its implicitserdedependency. This feature gated
Serialize/Deserializederives onProtocolandCompression, but the derived representations were incorrect(Rust variant names instead of spec values) and the feature only covered
these two enums. The equivalent feature was removed from the core
opentelemetrycrate in 2022.Migration: Remove
serialize(andserde, if listed) from your featurelist. If these values are part of serialisable app config, define a local
config enum or wrapper and convert it to
ProtocolorCompressionwhenbuilding the exporter.
#3711
Breaking Removed
reqwest-rustls-webpki-rootsfeature. Thewebpki-rootscargo feature wasremoved from
reqwestin v0.13.0, making this feature broken for anyone resolvingreqwest >= 0.13.0.Migration: Use
reqwest-rustlsinstead (now correctly usesreqwest/rustlswith platform nativetrust roots). If you specifically need Mozilla's embedded CA bundle, construct a custom client:
Allow to provide http client wrapped in Arc when configuring HTTP exporter. 3468
open-telemetry/opentelemetry-rust (opentelemetry_sdk)
v0.33.1Compare Source
Released 2026-Oct-08
PeriodicReaderworker thread panics (such as from an observable metric callback), and document
the callback panic contract.
(#3640)
Sampler::parent_based(root), returning aParentBasedSamplerthat letsall 5 branches of the ParentBased sampler spec be configured independently
(root, and remote/local parent that is/isn't sampled) via
with_remote_parent_sampled,with_remote_parent_not_sampled,with_local_parent_sampled, andwith_local_parent_not_sampled. PreviouslySampler::ParentBasedonly let youoverride the root case; the other 4 were fixed to the spec defaults. Unset
branches keep those same defaults, so this is purely additive.
(#3657)
Histogram,Sum,LastValue, andPrecomputedSumaggregators (andtheir bound-instrument handles) silently accepting NaN/Infinity
measurements. For
HistogramandSum, a single NaN measurementpermanently corrupted the cumulative
sum/total for the rest of theprocess's lifetime (
x + NaN == NaN);LastValueandPrecomputedSumself-healed on the next valid measurement but still exported one bad value
in the meantime, and
PrecomputedSumunder delta temporality corrupted twoexport cycles. Non-finite measurements are now dropped before recording,
matching
ExponentialHistogram's existing behavior.(#3656)
SdkTracerinheriting an invalid parent span context (e.g. a contextcarrying an invalid active span context). Such a parent is now treated as no
parent: the span gets a freshly generated trace id instead of the parent's
all-zero one, and is not recorded as a child of it.
(#3657)
PeriodicReader, makingfailures such as an unreachable collector visible without enabling DEBUG
logging.
(#3754)
v0.33.0Released 2026-Sep-18
OTEL_*/OTEL_*_DEFAULTenvironment variable name anddefault value constants for
BatchSpanProcessor(opentelemetry_sdk::trace),BatchLogProcessor(opentelemetry_sdk::logs), andPeriodicReader(
opentelemetry_sdk::metrics), so downstream configuration systems can readthe SDK's spec-defined defaults programmatically instead of duplicating
them. As part of this,
PeriodicReader's previously-privateDEFAULT_INTERVAL/METRIC_EXPORT_INTERVAL_NAMEconstants were renamedto
OTEL_METRIC_EXPORT_INTERVAL_DEFAULT/OTEL_METRIC_EXPORT_INTERVALtomatch the naming convention already used elsewhere.
(#3623)
experimental_metrics_bound_instruments:otel.sdk.log.createdcounts logrecords submitted to the SDK;
otel.sdk.processor.log.processedandotel.sdk.processor.span.processedcount records and spans submitted to anexporter by batch and simple processors, with
error.typereporting itemsdropped before submission; and
otel.sdk.processor.log.queue.capacityreports the configured
BatchLogProcessorqueue capacity.(#3514,
#3608,
#3609,
#3611)
futures-channel,futures-executor,futures-util, andthiserroroptional, enabling a minimal SDK build. With
default-features = false, theSDK's only dependency is the
opentelemetryAPI crate.(#3593)
GaugeandUpDownCountervia thenew
BoundGauge<T>andBoundUpDownCounter<T>types exposed by theopentelemetrycrate. Requires theexperimental_metrics_bound_instrumentsfeature.
BatchSpanProcessorandBatchLogProcessorwhere aspan/log enqueued just before
force_flush()orshutdown()could bemissed by the flush and dropped at shutdown: the pending-item counter is
now incremented before enqueueing (and reverted if the queue is full), so
the worker's counter snapshot can no longer under-count items already in
the queue (#3453).
unknown_serviceunderMiri instead of calling
std::env::current_exe(), avoiding an abort in Miriisolation mode while preserving the normal
unknown_service:<process.executable.name>fallback outside Miri.ObservableCounter,ObservableUpDownCounter)using delta temporality reporting incorrect deltas when observed attributes
were recorded in an unsorted key order.
rust-random/rand (rand)
v0.10.3Compare Source
Fixes
WeightedIndexpanic when the sum of float weights is infinite; returnError::Overflowinstead (#1808)Error::NonFinitefromUniform::new_inclusiveon large finite float ranges such as0.0..=f64::MAX(#1821)Uniform<char>(#1831)Changes
WeightedIndex::weights()and reduce overhead when reading weights (#1838)serde-rs/json (serde_json)
v1.0.154Compare Source
v1.0.153Compare Source
v1.0.152Compare Source
-0in arbitrary_precision mode (#1346, thanks @yuxi-liu-wired)dtolnay/thiserror (thiserror)
v2.0.21Compare Source
uuid-rs/uuid (uuid)
v1.28.0Compare Source
What's Changed
New Contributors
Full Changelog: uuid-rs/uuid@v1.27.0...v1.28.0
v1.27.0Compare Source
What's Changed
New Contributors
Full Changelog: uuid-rs/uuid@v1.26.1...v1.27.0
Configuration
📅 Schedule: (in timezone Etc/UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.