Skip to content

fix(deps): update all updates - #1820

Open
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/all-updates
Open

red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/all-updates

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Pending
hyper (source) dependencies minor 1.11.1 → 1.12.0
hyper-util (source) dependencies patch 0.1.20 → 0.1.21
libc workspace.dependencies patch 0.2.189 → 0.2.190 0.2.191
opentelemetry (source) dependencies minor 0.32.0 → 0.33.0
opentelemetry-otlp (source) dependencies minor 0.32.0 → 0.33.0
opentelemetry_sdk (source) dependencies minor 0.32.1 → 0.33.0
rand (source) dependencies patch 0.10.2 → 0.10.3
registry.access.redhat.com/ubi9/ubi final digest c5cc9c2 → 16e9e43
registry.access.redhat.com/ubi9/ubi stage digest c5cc9c2 → 16e9e43
registry.access.redhat.com/ubi9/ubi-micro stage digest 7a0454c → 5be877a
serde_json dependencies patch 1.0.151 → 1.0.154
thiserror dependencies patch 2.0.20 → 2.0.21
uuid dependencies minor 1.26.1 → 1.28.0

Release Notes

hyperium/hyper (hyper)

v1.12.0

Compare Source

Bug Fixes
  • http1:
    • withdraw a stale want when the client dispatcher takes a request (#​4208) (c44f1cc5)
    • remove content-length if transfer-encoding is auto-added (#​4224) (69396fdd)
    • always remove content-length if transfer-encoding is sent (#​4223) (a5d7fd78)
    • let a Connection close token win over a later keep-alive (#​4201) (5dadff76)
    • preserve hop-by-hop when setting close or keep-alive (#​4196) (74a39081)
  • http2: do not reserve capacity for idle Upgraded streams (#​4198) (e89d0d93)
Features
v1.11.1 (2026-08-27)
Bug Fixes
hyperium/hyper-util (hyper-util)

v0.1.21

Compare 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

  • Add crate-level documentation. (#​327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#​274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#​274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#​277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#​303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#​323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#​315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#​292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#​302)
  • Fix client::pool::cache to preserve readiness with clones. (#​297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#​298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#​299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#​296)
  • Fix client::proxy::matcher handling for IP wildcards. (#​309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#​276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#​302) (#​307) (#​308) (#​310)

Changes

This release contains a minor behavioral change for users of the tracing
feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled,
rt::TokioExecutor<E> began propagating the currently active tracing::Span
to spawned tasks when hyper::rt::Executor::execute() is called. This caused
issues 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::tracing
submodule, to provide facilities for instrumenting a client or server's spawned
tasks. See the module-level documentation of rt::tracing for more
information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation
behavior, enable the rt-tracing-exec-force feature. Note that this feature
flag will be removed in a future release.

rust-lang/libc (libc)

v0.2.190

Compare Source

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set
unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by
default:

  • 32-bit Linux-GNU
  • 32-bit Linux-uClibc
  • 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in
    musl v1.2.
  • 32-bit Windows-GNU
  • ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy
and 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 it
out and report any bugs you find!

Support
  • Add initial support for HelenOS (#​4355)
Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

  • Unix: Implement Default for a number of structs, especially on Apple platforms (#​5576)
  • Linux, NetBSD: Give statvfs a Default impl (#​5583)
  • Linux: Add Default to a linux/can.rs structs (#​5257)

Other additions:

  • Expose the libc_unstable_time64 cfg (#​5411)
  • Android, Glibc: Add pthread_gettid_np (#​5359)
  • Android: Add RTLD_NEXT (#​5323)
  • Android: Add reuseport BPF socket options (#​5366)
  • Apple: Add TCP header flags, options and SACK limits (#​5358)
  • Apple: Add NET_RT_DUMP2 (#​5442)
  • Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#​5558)
  • BSD: Add BPF_WORDALIGN (#​5320)
  • BSD: Add lchmod and lchflags where supported (#​5400)
  • BSD: Add minherit and related constants (#​4849)
  • Docs: Add more links to public headers and manual pages (#​5407), (#​5485)
  • Emscripten: Add epoll support (#​5427)
  • FreeBSD: Add AT_RENAME_* and RENAME_* constants (#​5560)
  • FreeBSD: Add renameat2 (#​5563)
  • FreeBSD: Add rt_msghdr and rt_metrics (#​5367)
  • Hurd: Add handling of LFS under libc_unstable_gnu_time_bits (#​5242)
  • Linux-GNU: Add environ (#​5339)
  • Linux-GNU: Add the new f_type field to statvfs and statvfs64 (#​5434)
  • Linux-like: Add additional STATX_* constants (#​5412)
  • Linux-musl, Emscripten: Add SIGEV_THREAD_ID (#​5375)
  • Linux-musl: Add *_SUPER_MAGIC constants (#​5453)
  • Linux-musl: Make statx always available (#​5448)
  • Linux-s390x: Add max_align_t (#​5389)
  • Linux: Add BCACHEFS_SUPER_MAGIC (#​5516)
  • Linux: Add ETH_P_LLDP (#​5438)
  • Linux: Add FUTEX_ROBUST_UNLOCK and FUTEX_ROBUST_LIST32 (#​5525)
  • Linux: Add NLMSG_* helpers (#​5321)
  • Linux: Update the definition of siginfo_t and add more getter functions (#​5345)
  • Musl riscv64: Add SYS_futex_waitv (#​5527)
  • Newlib: Add __errno (#​5346)
  • OpenBSD: Add RTLD_NODELETE and RTLD_NOLOAD (#​5377)
  • OpenBSD: Add getexecpath (#​5465)
  • OpenBSD: Add bindings from sensors.h (#​5510)
  • OpenBSD: Add missing HW_* sysctl constants (#​5371)
  • QNX: Add definitions for io-sock (#​5469)
  • Redox: Add FILENAME_MAX (#​5530)
  • Redox: Add clock_settime and pause (#​5363)
  • Redox: Add getrandom bindings (#​5333)
  • Unix: Add RFC 3678 multicast group_req/group_source_req and MCAST_* where supported (#​5236)
  • Unix: Add HOST_NAME_MAX (#​5531)
  • Unix: Add _PATH_BSHELL and _PATH_DEFPATH where available (#​5449)
  • WASI: Add SOCK_CLOEXEC (#​5336)
  • WASI: Add locale category constants (#​5378)
  • WASI: Add more pthread APIs (#​5310)
  • uClibc: Support 64-bit time_t on 32-bit platforms via cfg (#​5261)
Deprecated
  • AIX: deprecate _kernel_simple_lock (#​5380)
  • Deprecate integer *_MIN/*_MAX in favor of e.g. c_int::MAX (#​5404)
  • Fuchsia: Deprecate types that do not exist upstream (#​5127)
  • Hurd: Deprecate fallocate64, which does not exist on the platform (#​5242)
  • Hurd: Deprecate redundant glob64 types and routines (#​5242)
  • L4Re: deprecate LFS bindings (#​5173)
  • OpenBSD: Deprecate syscall, mincore, and KERN_NSELCOLL, all of which have been removed upstream (87992e9895c2)
  • Unix: Deprecate the POSIX-obsoleted tmpnam, tempnam (#​5478)
Fixed
  • breaking AIX: Change the type of BPF_ALIGNMENT to size_t to match upstream and harmonize with other platforms. (#​5373)
  • breaking Apple: change the type of BPF_ALIGNMENT to size_t to match upstream and harmonize with other platforms. (#​5348)
  • Exclude non-required repository files from the published crate (#​5312)
  • AIX: Correct the function signature in fileops_t.fo_select (#​5380)
  • AIX: Fix the alignment of file (#​5380)
  • Android: Add missing padding to ucontext_t (#​5189)
  • Android: Fix the value of RISC-V O_ flags (#​5554)
  • Fuchsia: Correct mcontext_t and ucontext_t and make them usable on more platforms (#​5127)
  • Fuchsia: Fix available fields in glob_t and statvfs (#​5127)
  • Fuchsia: Fix the definition of sigevent and correct the layout of other pthread.h types (#​5127)
  • Haiku: Correct the definition of sem_t (#​5351)
  • Linux-GNU: Fix the padding field in statvfs64 on 32-bit RISC-V (#​5518)
  • Linux: Correct PowerPC64 speed symbols with elfv2 (#​5342)
  • Linux: Fix syscall numbers on 32-bit RISC-V (#​5455)
  • Musl riscv64: Fix the definition of ipc_perm (#​5527)
  • Musl riscv64: Fix the name of the uc_flags field in ucontext_t (#​5527)
  • NetBSD: Fix WIFSTOPPED (#​5458)
  • Newlib: Update the time_t alias. This is a correction on Arm32 RTEMS (#​5132)
  • NuttX: Correct O_ open flags (#​5414)
  • RTEMS: Correct socket.h definitions (#​5313)
  • RTEMS: Correct the size of clock and storage type aliases (#​5450)
  • Redox: Correct signal.h types (#​5436)
Changed
  • The unstable cfg libc_unstable_musl_v1_2_3 has been renamed to a more accurate
    libc_unstable_musl_v1_2. The old version will continue to work for now, but will be removed in
    1-2 releases. (#​5376)
  • AIX: Make function pointers in signatures unsafe (#​5380)
  • Cygwin: Change POSIX_SPAWN_* flags to c_short (#​5572)
  • Hermit: Make iovec fields public (#​5460)
  • Improve the panic message for out-of-range fds in FD_* functions (#​5528)
  • Musl riscv64: Fix the name of __riscv_mc_q_ext_state.__reserved and make it private (#​5533)
  • Various: Make obsolete stat fields non-pub (#​5542)
  • uClibc: No longer link to libutil (#​5165)
Removed

libc exposed 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.

  • breaking Apple: Disable mach.h API on Apple mobile OSs (e6bfb187513c)
  • breaking Apple: Remove a large number of items from iOS, tvOS, watchOS, and visionOS that are only available on MacOS. (#​5158)
  • breaking Apple: Remove the unsupported exec* and fork calls 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.

  • breaking Android, Linux: remove unsound af_alg_iv trait implementations. The have been deprecated for a long time because they allowed out-of-bounds reads via safe functions. (444db4456f38)
  • breaking Remove most items that have been deprecated since before 0.2.100 (#​5401)

Other removed items:

  • Dragonfly: Remove INHERIT_ZERO that does not exist upstream (#​5587)
  • Musl riscv64: Remove GNU-gated REG_* definitions (#​5527)
  • Musl riscv64: Remove non-esxistant 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.1

Compare Source

Released 2026-Oct-08

  • Fix a panic when a value stored with Context::with_value() calls
    Context::current() from its Drop implementation.
  • Expand tracing documentation on async context propagation and child spans
    (#​828).
  • Document the panic contract for observable metric callbacks (Callback and
    AsyncInstrumentBuilder::with_callback).
    (#​3640)
  • Fix TraceState::from_str rejecting valid optional whitespace around list members.
    (#​3757)

v0.33.0

Compare Source

Released 2026-Sep-18

  • Fix TraceState accepting more than the 32 list-members the W3C trace-context
    specification allows. from_str, from_key_value and insert now keep at most
    32, dropping members from the end of the list as the specification prescribes, so
    neither a parsed nor a locally built tracestate can exceed the limit.
  • Added experimental support for a global context event observer. A
    ContextObserver can be registered via GlobalContextObserver::set to be
    notified of context transitions through the on_context_enter and
    on_context_exit callbacks. This feature is primarily intended to publish a
    different view of the current context (the ObserverContextView) through
    alternative channels that let external readers (e.g. an eBPF profiler) track
    the current context. See the associated
    OTEP.
    Gated behind the experimental_context_observer feature flag.
  • otel_info!, otel_warn!, otel_debug!, and otel_error! macros now accept quoted-key fields
    (e.g. "otel.component.type" = "value") for dotted attribute names.
  • Added BoundGauge<T> and BoundUpDownCounter<T> types (and the
    corresponding Gauge::bind() / UpDownCounter::bind() methods), completing
    the experimental bound-instrument API across all sync instruments
    (Counter, UpDownCounter, Histogram, Gauge). Gated behind the
    experimental_metrics_bound_instruments feature flag.
open-telemetry/opentelemetry-rust (opentelemetry-otlp)

v0.33.1

Compare Source

Released 2026-Oct-08

  • Declare the OTLP exporters for Logs and Metrics stable after the 0.33.0 release-candidate period. Tracing remains in beta.
  • Update OpenTelemetry dependencies to 0.33.1, including SDK fixes and OTLP/JSON interoperability fixes in opentelemetry-proto.

v0.33.0

Compare 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 opaque ParseConfigError
    instead of ExporterBuildError. Update explicit result types and error handling
    that expects ExporterBuildError::UnsupportedCompressionAlgorithm. The new error
    implements Display and std::error::Error; its message is for diagnostics.
    Accepted strings and parsing behavior are unchanged.

    // Before:
    let result: Result<Compression, ExporterBuildError> = value.parse();
    
    // After:
    let result: Result<Compression, ParseConfigError> = value.parse();
    if let Err(error) = result {
        eprintln!("invalid compression configuration: {error}");
    }
  • 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 none explicitly
    disables compression, including when a generic compression value is set.
    Programmatic configuration remains strict.

Retry
  • Retries are now enabled by default for OTLP/HTTP and OTLP/gRPC. The default
    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 RetryPolicy to change the behavior.
  • Migration for users of the experimental retry features: If your
    Cargo.toml enables experimental-grpc-retry or
    experimental-http-retry, remove those feature flags. No migration action is
    required for users who did not enable them.
    #​3621
  • Breaking Make the retry and retry_classification modules crate-private,
    removing their retry engine, error type, and protocol classifiers from the
    public API. RetryPolicy remains available from the crate root with private
    fields and fluent configuration methods. Replace imports from
    opentelemetry_otlp::retry with opentelemetry_otlp::RetryPolicy, and replace
    struct literals with its with_* methods.
    #​3672
Retry fixes

The following fixes apply to retry behavior that was experimental before this
release:

  • Retry only HTTP status codes 429, 502, 503, and 504, as required by the OTLP
    specification. The exporter now also honors Retry-After on 503 responses.
  • Honor positive gRPC RetryInfo delays returned with Unavailable responses.
  • Continue exponential backoff from server-provided RetryInfo and
    Retry-After delays 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 conversion
    callers:
    removed TryFrom<Compression> for
    tonic::codec::CompressionEncoding. Code explicitly converting between these
    enums 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 Default from the TonicExporterBuilderSet and
    HttpExporterBuilderSet typestate markers. This also removes Default from
    the transport-selected exporter builders (e.g.
    SpanExporterBuilder<TonicExporterBuilderSet>). Use the intended builder
    flow instead:

    // Before (no longer compiles):
    let exporter = SpanExporterBuilder::<TonicExporterBuilderSet>::default().build()?;
    
    // After (use the builder entry point):
    let exporter = SpanExporter::builder().with_tonic().build()?;

    Also removed the unused #[doc(hidden)] NoExporterConfig type.

  • Breaking Mark Protocol and Compression as non-exhaustive so new OTLP
    protocols, 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.

    let protocol_name = match protocol {
        Protocol::Grpc => "grpc",
        Protocol::HttpBinary => "http/protobuf",
        Protocol::HttpJson => "http/json",
        _ => "unknown", // Required because Protocol is non-exhaustive.
    };
  • Breaking Make Protocol::from_env() crate-private. Exporter builders
    already resolve OTEL_EXPORTER_OTLP_PROTOCOL when built; applications that
    need to inspect the raw environment setting should read the variable
    directly.

  • Breaking Remove OTEL_EXPORTER_OTLP_ENDPOINT_DEFAULT, which always held
    the HTTP default (http://localhost:4318) despite gRPC using
    http://localhost:4317. Omit .with_endpoint(...) to let the selected
    transport use its correct default, or provide the appropriate URL explicitly.
    #​3690

  • Breaking Restrict MetricExporterBuilder::with_http() and with_tonic()
    to builders where no transport has been selected, matching the span and log
    exporter builders. Select a transport once; with_temporality() remains
    available before or after transport selection.

  • Breaking Remove the public HttpExporterBuilder and
    TonicExporterBuilder transport-first APIs. Configure transports through the
    signal builders instead:

    • Replace HttpExporterBuilder::default() with the corresponding signal
      exporter builder followed by .with_http(), then replace
      .build_span_exporter() or .build_log_exporter() with .build().
    • Replace .build_metrics_exporter(temporality) with
      .with_temporality(temporality).build().
    • Replace TonicExporterBuilder::default() with the corresponding signal
      exporter builder followed by .with_tonic().
      Transport-specific configuration methods remain available after
      .with_http() or .with_tonic().
  • Breaking Removed the deprecated tls feature alias. Replace tls with
    tls-ring, or select tls-aws-lc or tls-provider-agnostic explicitly.

  • Exporter builder usage is unchanged. Breaking for code matching or constructing
    removed error variants:
    Simplified ExporterBuildError to the exhaustive
    InvalidConfiguration(String) and InternalFailure(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-exhaustive
    matches such as:

    match error {
        ExporterBuildError::InvalidUri(_, _)
        | ExporterBuildError::InvalidConfig { .. }
        | ExporterBuildError::NoHttpClient => {
            eprintln!("fix the exporter configuration");
        }
        ExporterBuildError::InternalFailure(message) => {
            eprintln!("exporter initialization failed: {message}");
        }
        _ => {}
    }

    with an exhaustive match over the two stable categories:

    match error {
        ExporterBuildError::InvalidConfiguration(message) => {
            eprintln!("fix the exporter configuration: {message}");
        }
        ExporterBuildError::InternalFailure(message) => {
            eprintln!("exporter initialization failed: {message}");
        }
    }

    Code that propagates build errors with ? without inspecting their variants
    needs 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_size to configure the HTTP request
    body 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, and
    WithTonicConfig. These traits remain public for calling configuration
    methods 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=true uses http://, INSECURE=false (default) uses https:// with auto-TLS.
    Breaking: Schemeless endpoints (e.g., collector.example.com:4317) now default to https://
    instead of being passed as-is. Set OTEL_EXPORTER_OTLP_INSECURE=true for plaintext connections.
    Endpoints with an explicit scheme (e.g., http://, https://, unix://) are unaffected.
    #​774
    #​984

  • Breaking Removed the serialize feature flag and its implicit serde
    dependency. This feature gated Serialize/Deserialize derives on
    Protocol and Compression, 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
    opentelemetry crate in 2022.
    Migration: Remove serialize (and serde, if listed) from your feature
    list. If these values are part of serialisable app config, define a local
    config enum or wrapper and convert it to Protocol or Compression when
    building the exporter.
    #​3711

  • Breaking Removed reqwest-rustls-webpki-roots feature. The webpki-roots cargo feature was
    removed from reqwest in v0.13.0, making this feature broken for anyone resolving reqwest >= 0.13.0.
    Migration: Use reqwest-rustls instead (now correctly uses reqwest/rustls with platform native
    trust roots). If you specifically need Mozilla's embedded CA bundle, construct a custom client:

    let root_store = rustls::RootCertStore::from_iter(
        webpki_roots::TLS_SERVER_ROOTS.iter().cloned(),
    );
    let tls_config = rustls::ClientConfig::builder()
        .with_root_certificates(root_store)
        .with_no_client_auth();
    let client = reqwest::Client::builder()
        .tls_backend_preconfigured(tls_config)
        .build()?;
    exporter_builder.with_http_client(client)
  • Allow to provide http client wrapped in Arc when configuring HTTP exporter. 3468

open-telemetry/opentelemetry-rust (opentelemetry_sdk)

v0.33.1

Compare Source

Released 2026-Oct-08

  • Emit a one-time internal error diagnostic when the default PeriodicReader
    worker thread panics (such as from an observable metric callback), and document
    the callback panic contract.
    (#​3640)
  • Added Sampler::parent_based(root), returning a ParentBasedSampler that lets
    all 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, and
    with_local_parent_not_sampled. Previously Sampler::ParentBased only let you
    override the root case; the other 4 were fixed to the spec defaults. Unset
    branches keep those same defaults, so this is purely additive.
    (#​3657)
  • Fixed Histogram, Sum, LastValue, and PrecomputedSum aggregators (and
    their bound-instrument handles) silently accepting NaN/Infinity
    measurements. For Histogram and Sum, a single NaN measurement
    permanently corrupted the cumulative sum/total for the rest of the
    process's lifetime (x + NaN == NaN); LastValue and PrecomputedSum
    self-healed on the next valid measurement but still exported one bad value
    in the meantime, and PrecomputedSum under delta temporality corrupted two
    export cycles. Non-finite measurements are now dropped before recording,
    matching ExponentialHistogram's existing behavior.
    (#​3656)
  • Fixed SdkTracer inheriting an invalid parent span context (e.g. a context
    carrying 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)
  • Log metric export failures at ERROR level in PeriodicReader, making
    failures such as an unreachable collector visible without enabling DEBUG
    logging.
    (#​3754)

v0.33.0

Released 2026-Sep-18

  • Publicly export the OTEL_*/OTEL_*_DEFAULT environment variable name and
    default value constants for BatchSpanProcessor (opentelemetry_sdk::trace),
    BatchLogProcessor (opentelemetry_sdk::logs), and PeriodicReader
    (opentelemetry_sdk::metrics), so downstream configuration systems can read
    the SDK's spec-defined defaults programmatically instead of duplicating
    them. As part of this, PeriodicReader's previously-private
    DEFAULT_INTERVAL/METRIC_EXPORT_INTERVAL_NAME constants were renamed
    to OTEL_METRIC_EXPORT_INTERVAL_DEFAULT/OTEL_METRIC_EXPORT_INTERVAL to
    match the naming convention already used elsewhere.
    (#​3623)
  • Added SDK self-observability metrics, feature-gated behind
    experimental_metrics_bound_instruments: otel.sdk.log.created counts log
    records submitted to the SDK; otel.sdk.processor.log.processed and
    otel.sdk.processor.span.processed count records and spans submitted to an
    exporter by batch and simple processors, with error.type reporting items
    dropped before submission; and otel.sdk.processor.log.queue.capacity
    reports the configured BatchLogProcessor queue capacity.
    (#​3514,
    #​3608,
    #​3609,
    #​3611)
  • Made futures-channel, futures-executor, futures-util, and thiserror
    optional, enabling a minimal SDK build. With default-features = false, the
    SDK's only dependency is the opentelemetry API crate.
    (#​3593)
  • Bound instruments are now available for Gauge and UpDownCounter via the
    new BoundGauge<T> and BoundUpDownCounter<T> types exposed by the
    opentelemetry crate. Requires the experimental_metrics_bound_instruments
    feature.
  • Fixed a race in BatchSpanProcessor and BatchLogProcessor where a
    span/log enqueued just before force_flush() or shutdown() could be
    missed 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).
  • Default SDK Resource construction now falls back to unknown_service under
    Miri instead of calling std::env::current_exe(), avoiding an abort in Miri
    isolation mode while preserving the normal
    unknown_service:<process.executable.name> fallback outside Miri.
  • Fixed asynchronous counters (ObservableCounter, ObservableUpDownCounter)
    using delta temporality reporting incorrect deltas when observed attributes
    were recorded in an unsorted key order.
rust-random/rand (rand)

v0.10.3

Compare Source

Fixes
  • Fix WeightedIndex panic when the sum of float weights is infinite; return Error::Overflow instead (#​1808)
  • Fix spurious Error::NonFinite from Uniform::new_inclusive on large finite float ranges such as 0.0..=f64::MAX (#​1821)
  • Fix possible panic due to sampling a deserialized Uniform<char> (#​1831)
Changes
  • Report exact remaining lengths from WeightedIndex::weights() and reduce overhead when reading weights (#​1838)
serde-rs/json (serde_json)

v1.0.154

Compare Source

v1.0.153

Compare Source

v1.0.152

Compare Source

dtolnay/thiserror (thiserror)

v2.0.21

Compare Source

  • Fix parsing of generic unit variants in display expressions (#​459)
uuid-rs/uuid (uuid)

v1.28.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.27.0...v1.28.0

v1.27.0

Compare Source

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.26.1...v1.27.0


Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

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.

@red-hat-konflux
red-hat-konflux Bot requested review from a team and rhacs-bot as code owners September 18, 2026 02:00
@red-hat-konflux
red-hat-konflux Bot enabled auto-merge (squash) September 18, 2026 02:00
@coderabbitai

coderabbitai Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

Note

Reviews paused

It 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 reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: stackrox/fact/.coderabbit.yml
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: e478ab89-72ce-438e-aa6b-2cebb0d9092f
📥 Commits

Reviewing files that changed from the base of the PR and between d7f0b48 and ecae7bd.

📒 Files selected for processing (1)
  • Cargo.toml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 9 remain after this review.

📝 Walkthrough

The pull request updates the Aya Git revision, the optional OpenTelemetry dependency versions, and the UBI 9 image digest used by the package_installer and builder stages.

Changes: Rust Dependency Updates

Layer / File(s) Summary
Update dependency pins
Cargo.toml, fact/Cargo.toml
The Aya Git revision changes. Its Git source and disabled default features remain unchanged. The optional OpenTelemetry dependencies change to version 0.33.0; the SDK retains its logs feature.

Container Image Updates

Layer / File(s) Summary
Update stage image digests
konflux.Containerfile
The package_installer and builder stages switch to the updated UBI 9 image digest.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: molter73

Merge Risk: 🔵 Low · up to ecae7

Regenerate Cargo.lock before relying on the dependency updates; ordinary unlocked builds may refresh it, but locked builds can fail or retain the previous revisions.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
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.

@red-hat-konflux

red-hat-konflux Bot commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path fact/Cargo.toml --package hyper@1.11.1 --precise 1.12.0
    Updating crates.io index
    Updating git repository `https://github.com/aya-rs/aya.git`
error: failed to get `aya` as a dependency of package `fact v0.5.0-dev (/tmp/renovate/repos/github/stackrox/fact/fact)`

Caused by:
  failed to load source for dependency `aya`

Caused by:
  unable to update https://github.com/aya-rs/aya.git?rev=c29cd71cb4fe1440bc0d566633afa822f1b41fc5#c29cd71c

Caused by:
  failed to create directory `/home/renovate/.cargo/git/db/aya-c5ab473414e1dedb`

Caused by:
  Permission denied (os error 13)

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package libc@0.2.189 --precise 0.2.190
    Updating crates.io index
    Updating git repository `https://github.com/aya-rs/aya.git`
error: failed to get `aya` as a dependency of package `fact v0.5.0-dev (/tmp/renovate/repos/github/stackrox/fact/fact)`

Caused by:
  failed to load source for dependency `aya`

Caused by:
  unable to update https://github.com/aya-rs/aya.git?rev=c29cd71cb4fe1440bc0d566633afa822f1b41fc5#c29cd71c

Caused by:
  failed to create directory `/home/renovate/.cargo/git/db/aya-c5ab473414e1dedb`

Caused by:
  Permission denied (os error 13)

@rhacs-bot rhacs-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved by automation.

@codecov-commenter

codecov-commenter commented Sep 18, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 33.45%. Comparing base (4e36655) to head (cf2b267).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch 6 times, most recently from 2e31e3a to cc5ae41 Compare September 21, 2026 01:36
@Molter73

Copy link
Copy Markdown
Member

/konflux-retest fact-on-push

@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch from cc5ae41 to 622bc03 Compare September 22, 2026 04:55
@red-hat-konflux red-hat-konflux Bot changed the title chore(deps): update all updates fix(deps): update all updates Sep 22, 2026
@Molter73

Copy link
Copy Markdown
Member

/konflux-retest fact-on-push

@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch from 622bc03 to eb0be13 Compare September 23, 2026 02:44
@Molter73

Copy link
Copy Markdown
Member

/konflux-retest fact-on-push

@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch from eb0be13 to c00631e Compare September 23, 2026 09:21
@Molter73

Copy link
Copy Markdown
Member

/konflux-retest fact-on-push

@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch 6 times, most recently from 95c720f to b0640d7 Compare September 27, 2026 00:57
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch 12 times, most recently from 7fdc890 to c52c3ec Compare October 12, 2026 01:04
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch 5 times, most recently from 284ce05 to a703b5e Compare October 14, 2026 05:11
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch 7 times, most recently from 6444d03 to ea6bf2c Compare October 18, 2026 00:55
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main/all-updates branch from ea6bf2c to cf2b267 Compare October 18, 2026 04:58
@github-actions

Copy link
Copy Markdown

/konflux-retest fact-on-push

2 similar comments
@github-actions

Copy link
Copy Markdown

/konflux-retest fact-on-push

@github-actions

Copy link
Copy Markdown

/konflux-retest fact-on-push

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants