chore(deps): bump opentelemetry from 0.31.0 to 0.32.0#4947
Merged
Conversation
Bumps [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust) from 0.31.0 to 0.32.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md) - [Commits](open-telemetry/opentelemetry-rust@opentelemetry-prometheus-0.31.0...opentelemetry-0.32.0) --- updated-dependencies: - dependency-name: opentelemetry dependency-version: 0.32.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
the
dependencies
houko
added a commit
that referenced
this pull request
May 12, 2026
…#4953) dependabot #4947 bumped `opentelemetry` to 0.32 but `[email protected]` (the latest release) still pins `opentelemetry = "0.31"`. After the bump the dependency tree contained two copies of `opentelemetry::trace::Tracer` — the 0.31 trait that tracing-opentelemetry uses, and the 0.32 trait that `SdkTracerProvider::tracer()` returns — and `telemetry.rs:153` (`tracing_opentelemetry::layer().with_tracer(tracer)`) failed `SdkTracer: Tracer` trait bound resolution. Effect: main CI was failing every PR with E0599 \"no method named 'tracer' found for struct 'SdkTracerProvider'\" on Test/Unit, Test/macOS, Test/Windows, Test/Ubuntu shards, Quality, Live Integration Smoke, OpenAPI Drift, and llvm-cov. Revert opentelemetry, opentelemetry_sdk, and opentelemetry-otlp to 0.31; keep tracing-opentelemetry at 0.32 (still on the 0.31 train). Add a doc-comment guarding the next bump on tracing-opentelemetry publishing a 0.31→0.32 follow-up. cargo check -p librefang-api → clean.
GQAdonis
added a commit
to GQAdonis/librefang
that referenced
this pull request
May 19, 2026
Merges 10 further upstream librefang/librefang commits onto the 2026-05-17 merge (channel-adapter pruning: drops 18 in-process adapters across librefang#5265/librefang#5267, migrates mastodon/gotify to sidecars, dep bumps). Conflict resolution (7 files): - librefang-api / librefang-cli Cargo.toml: kept surreal-backend in the default feature set, merged upstream's updated channel-set comment. - docs architecture + integrations pages (en + zh): took upstream's channel-adapter content (in-process set + sidecar note, IRC/Mumble doc sections removed) but kept BossFang surface strings ("BossFang Protocol", not "LibreFang Protocol"). - Cargo.lock: regenerated; surreal-memory 95a83b6 / UAR 0f9385d pins preserved. Post-merge fixes (build breakage surfaced under default `surreal-backend`): - Cargo.toml: reverted upstream's opentelemetry-otlp 0.31 -> 0.32 bump. The in-repo comment forbids 0.32 until tracing-opentelemetry depends on opentelemetry 0.32 (0.32.1 still pins 0.31); 0.32 leaves two opentelemetry trees and breaks the SpanExporter trait bound in telemetry.rs. Same revert dependabot librefang#4947 already had. - context_engine/scriptable/mod.rs: restored BossFang's TraceBackend abstraction the 2026-05-17 merge dropped — `trace_store` field re-typed to `Arc<dyn TraceBackend>`, added `with_trace_backend` builder (the context_engine.rs caller already expects it), moved circuit-breaker restore into it (backend is injected after with_plugin_name). Disambiguated a `Memory::remember` call. - kernel-metering/lib.rs: `MeteringEngine::new` was missing the `exhaustion: None` field; dropped an unused `UsageStore` import. - routes/agents.rs: `CloneAgentRequest` reverted pub(crate) -> pub — the `clone_agent` handler is registered by the librefang-testing router builder, so pub(crate) leaked a private type cross-crate. SurrealDB schema parity: no new .surql migration required (no upstream SQLite schema changes in this batch). Verification: - cargo check --workspace --lib: PASS - cargo check -p librefang-llm-drivers --features uar-driver -p librefang-storage -p librefang-uar-spec -p librefang-memory: PASS - python3 scripts/enforce-branding.py --check: PASS (exit 0) - Tauri audit: productName BossFang, ai.bossfang.* identifiers, GQAdonis updater endpoint, minisign key E329A6B2863F1707 — intact.
This was referenced May 19, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps opentelemetry from 0.31.0 to 0.32.0.
Release notes
Sourced from opentelemetry's releases.
Changelog
Sourced from opentelemetry's changelog.
... (truncated)
Commits
ec289cbchore: Prepare for release v0.32.0 (#3508)3ddb386fix(metrics): reject usize::MAX as cardinality limit (#3506)bad0a1bfeat(appender-tracing): re-gate span attribute enrichment behind experimental...f744509docs: update README status table and remove deprecated crates (#3502)81d5a06chore(prometheus): restore crate to workspace (#3500)5a07ce1ci: close stale pull requests (#3499)cc87dd9feat(appender-tracing): stabilize span attribute propagation (#3482)f290595docs(metrics): document experimental bound instruments (#3495)a79eb76fix(sdk): suppress telemetry in SimpleSpanProcessor during export (#3494)aa3bda3chore(zipkin): deprecate opentelemetry-zipkin crate (#3492)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)