Update `opentelemetry` Rust crates by hash-worker[bot] · Pull Request #8013 · hashintel/hash

hash-worker · 2025-11-05T00:34:20Z

This PR contains the following updates:

Package	Type	Update	Change	Pending
opentelemetry (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`
opentelemetry-appender-tracing (source)	workspace.dependencies	minor	`0.30.1` → `0.32.0`
opentelemetry-otlp (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`
opentelemetry-semantic-conventions (source)	workspace.dependencies	minor	`0.30.0` → `0.32.0`	`0.32.1`
tracing-opentelemetry	workspace.dependencies	minor	`0.31.0` → `0.33.0`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

open-telemetry/opentelemetry-rust (opentelemetry)

`v0.32.0`

Compare Source

Released 2026-May-08

Added BoundCounter<T> and BoundHistogram<T> types that cache resolved
aggregator references for a fixed attribute set. Created via Counter::bind()
and Histogram::bind(), bound instruments bypass per-call attribute lookup,
providing significant performance improvements for hot paths where the same
attributes are used repeatedly. Both types implement Clone so a single bound
state can be shared across threads or modules without re-binding. Also adds
the SyncInstrument::bind() trait method and BoundSyncInstrument<T> trait
for SDK implementors; the trait method has a no-op default so custom
SyncInstrument impls degrade gracefully without panicking. Gated behind the
experimental_metrics_bound_instruments feature flag.
Add reserve method to opentelemetry::propagation::Injector to hint at the number of elements that will be added to avoid multiple resize operations of the underlying data structure. Has an empty default implementation.
Breaking Removed the following public fields and methods from the SpanBuilder #3227:
- trace_id, span_id, end_time, status, sampling_result
- with_trace_id, with_span_id, with_end_time, with_status, with_sampling_result
Added #[must_use] attribute to opentelemetry::metrics::AsyncInstrumentBuilder to add compile time warning when .build() is not called on observable instrument builders, preventing silent failures where callbacks are never registered and metrics are never reported.
Breaking Moved the following SDK sampling types from opentelemetry::trace to opentelemetry_sdk::trace #3277:
- SamplingDecision, SamplingResult
- These types are SDK implementation details and should be imported from opentelemetry_sdk::trace instead.
"spec_unstable_logs_enabled" feature flag is removed. The capability (and the
backing specification) is now stable and is enabled by default.
3278
Remove the empty "message" field from tracing events emitted via the internal-logs feature
Fix panic when calling Context::current() from Drop implementations triggered by ContextGuard cleanup (#3262).

`v0.31.0`

Compare Source

Released 2025-Sep-25

Breaking Change return type of opentelemetry::global::set_tracer_provider to Unit to align with metrics counterpart
Add get_all method to opentelemetry::propagation::Extractor to return all values of the given propagation key and provide a default implementation.
Add an IntoIterator implementation for opentelemetry::trace::TraceState to allow iterating through its key-value pair collection.

open-telemetry/opentelemetry-rust (opentelemetry-appender-tracing)

`v0.32.0`

Released 2026-May-08

Add tracing span attribute enrichment (experimental). When enabled,
attributes attached to active tracing spans are copied onto each emitted
log record. "Span" here refers to a tracing::span! from the
tracing crate (the appender's source), not an OpenTelemetry span.
#3482, #3505

Gated behind the new experimental_span_attributes cargo feature. As
with all experimental_* features in this repo, the API may change without
a major version bump until it is stabilized; once stable, the feature flag
will be removed.

Enrichment is disabled by default (no per-span overhead) and must be
opted into at runtime via a single builder method that accepts a
[TracingSpanAttributes] value:
```
use opentelemetry_appender_tracing::layer::TracingSpanAttributes;

// Copy all tracing-span attributes onto log records:
let layer = OpenTelemetryTracingBridge::builder(&provider)
    .with_tracing_span_attributes(TracingSpanAttributes::all())
    .build();

// Or copy only an allowlist of attributes:
let layer = OpenTelemetryTracingBridge::builder(&provider)
    .with_tracing_span_attributes(TracingSpanAttributes::allowlist(["session.id"]))
    .build();
```
Remove the experimental_use_tracing_span_context since
tracing-opentelemetry now supports activating the OpenTelemetry
context for the current tracing span. This fixes #3190 — the
circular dependency introduced by depending on tracing-opentelemetry
that depends on opentelemetry.
"spec_unstable_logs_enabled" feature flag is removed. The capability (and the
backing specification) is now stable and is enabled by default. #3278

`v0.31.1`

Released 2025-Oct-1

Bump tracing-opentelemetry to 0.32

`v0.31.0`

Released 2025-Sep-25

Updated opentelemetry dependency to version 0.31.0.

open-telemetry/opentelemetry-rust (opentelemetry-otlp)

`v0.32.0`

Compare Source

Released 2026-May-08

Add tls-provider-agnostic feature flag for environments that require a custom crypto backend (e.g., OpenSSL for FIPS compliance). Enables TLS code paths without bundling ring or aws-lc-rs.
Add build() directly on SpanExporterBuilder, MetricExporterBuilder, and LogExporterBuilder
(before selecting a transport), which auto-selects the transport based on the
OTEL_EXPORTER_OTLP_PROTOCOL environment variable or enabled features.
#3394
Breaking Removed ExportConfig, HasExportConfig, with_export_config(), HasTonicConfig, HasHttpConfig, TonicConfig, and HttpConfig from public API.
Use the public WithExportConfig, WithTonicConfig, and WithHttpConfig trait methods instead, which remain unchanged.
The gRPC/tonic OTLP exporter's build method now returns an error for all signals (traces, metrics, logs) when
an https:// endpoint is configured but no TLS feature (tls-ring or tls-aws-lc) is enabled, instead of
silently sending unencrypted traffic. When a TLS feature is enabled and an https:// endpoint is used without
an explicit .with_tls_config(), a default ClientTlsConfig is automatically applied.
#3182
Prevent auth tokens from leaking in export error messages. gRPC and HTTP
exporter errors no longer include potentially sensitive server responses
(e.g., authentication tokens echoed back). Error messages returned to SDK
processors contain only the gRPC status code or HTTP status code. Full
details are logged at DEBUG level only.
#3021
Surface pre-flight transport error details at ERROR level when grpc-tonic
OTLP export fails due to a local misconfiguration. When the returned
tonic::Status wraps a local transport error (invalid URL, connect failure,
DNS), its source chain (e.g., "transport error: invalid URI") is appended
to the returned error so SDK processors surface it at ERROR without
requiring DEBUG logging. Server-returned gRPC status messages remain
DEBUG-only to preserve the auth-token leak safeguards from
#3021.
#3331
Add support for per-signal protocol environment variables:
OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, OTEL_EXPORTER_OTLP_METRICS_PROTOCOL,
OTEL_EXPORTER_OTLP_LOGS_PROTOCOL. These allow configuring different transport protocols
per signal type. Signal-specific vars take precedence over generic OTEL_EXPORTER_OTLP_PROTOCOL.
The auto-select build() method on each exporter builder now respects the full priority chain:
signal-specific env var > generic env var > feature-based default.
Transport/protocol mismatch validation: HTTP transport returns InvalidConfig when gRPC protocol
is requested; gRPC transport returns InvalidConfig when an HTTP protocol is requested.
Breaking: Protocol::default() no longer consults the OTEL_EXPORTER_OTLP_PROTOCOL
environment variable. It now returns only the feature-based default (http-json > http-proto >
grpc-tonic). Protocol resolution from environment variables is handled internally by the
exporter builders. Users who relied on Protocol::default() to read env vars should use
Protocol::from_env() instead.
Add support for OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE environment variable
to configure metrics temporality. Accepted values: cumulative (default), delta,
lowmemory (case-insensitive). Programmatic .with_temporality() overrides the env var.
Fix NoHttpClient error when multiple HTTP client features are enabled by using priority-based selection (reqwest-client > hyper-client > reqwest-blocking-client). #2994
Add partial success response handling for OTLP exporters (traces, metrics, logs) per OTLP spec. Exporters now log warnings when the server returns partial success responses with rejected items and error messages. #865
Refactor internal-logs feature in opentelemetry-otlp to reduce unnecessary dependencies3191
Fixed [#2777](https://github.com/open-telemetry/opentelemetry rust/issues/2777) to properly handle shutdown_with_timeout() when using grpc-tonic.
Deprecate tls feature in favor of explicit tls-ring and tls-aws-lc features.
Migration: Replace tls with tls-ring (or tls-aws-lc). Users of tls-roots or tls-webpki-roots must now also enable one of these.
Prevent logging of header values in OTLP tonic exporter #3465

`v0.31.1`: opentelemetry-otlp 0.31.1

Compare Source

What's Changed

feat(OTLP): add tls-ring, tls-aws-lc, and tls-provider-agnostic feature flags [patch release v0.31.1] by @lalitb in #3426

Full Changelog: open-telemetry/opentelemetry-rust@v0.31.0...opentelemetry-otlp-0.31.1

`v0.31.0`

Compare Source

Released 2025-Sep-25

Update opentelemetry-proto and opentelemetry-http dependency version to 0.31.0
Add HTTP compression support with gzip-http and zstd-http feature flags
Add retry with exponential backoff and throttling support for HTTP and gRPC exporters
This behaviour is opt in via the experimental-grpc-retry and experimental-http-retry flags on this crate. You can customize the retry policy using the with_retry_policy on the exporter builders.

open-telemetry/opentelemetry-rust (opentelemetry-semantic-conventions)

`v0.32.0`

Compare Source

Released 2026-May-08

`v0.31.0`

Compare Source

Released 2025-Sep-25

Update to v1.34.0 of the semantic conventions.

tokio-rs/tracing-opentelemetry (tracing-opentelemetry)

`v0.33.0`

Compare Source

Fixed

[breaking] avoid deadlock when entering a span (#251)

Other

Upgrade to OpenTelemetry 0.32, see upstream changelog for details (#258)
mimimize package size (#252)

`v0.32.1`

Compare Source

Added

allow OpenTelemetry context access with SpanRef (#234)
add event-counting filtering layer for spans (#228)
publicly export SetParentError

Fixed

fix panic in multithreaded follows-from

Other

Remove unwanted dependency on opentelemetry sdk crate (#241)
update README.md links to use the latest version (#239)
remove thiserror and unused dependencies (#238)

`v0.32.0`

Compare Source

Added

Add configuration for including target in spans (#222)

Changed

OpenTelemetry context activation (#202)
- Trace ID and span ID can be obtained from OtelData via dedicated functions. Note that these
  will be available only if the context has already been built. (#233)
Correctly track entered and exited state for timings (#212)
Slightly improve error message on version mismatch (#211)
Remove Lazy for thread_local static (#215)
Update description of special fields and semantic conventions

Breaking Changes

The attributes code.filepath, code.lineno, and code.namespace have been renamed to
code.file.path, and code.line.number, and code.module.name, to align with the opentelemetry
semantic conventions for code. (#225)
Upgrade from opentelemetry to 0.31.0. Refer to the upstream
changelog
for more information. (#230)
Hold onto MetricsProvider in MetricsLayer (#224)
The attribute otel.status_message was changed to otel.status_description to align with the
opentelemetry semantic conventions for code. (#209)
Remove the metrics_gauge_unstable feature.

Configuration

📅 Schedule: (UTC)

Branch creation
- "before 4am every weekday,every weekend"
Automerge
- "before 4am every weekday,every weekend"

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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

This PR has been generated by Renovate Bot.

vercel · 2025-11-19T13:51:04Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ds-theme	Ready	Preview, Comment	Jun 28, 2026 1:40am
hash	Ready	Preview, Comment	Jun 28, 2026 1:40am
hashdotdesign	Ready	Preview, Comment	Jun 28, 2026 1:40am
hashdotdesign-tokens	Ready	Preview, Comment	Jun 28, 2026 1:40am
petrinaut	Ready	Preview	Jun 28, 2026 1:40am

codecov · 2025-11-19T13:56:06Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.77%. Comparing base (b8f5e58) to head (5149cd2).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8013      +/-   ##
==========================================
- Coverage   59.77%   59.77%   -0.01%     
==========================================
  Files        1348     1348              
  Lines      131787   131833      +46     
  Branches     5941     5941              
==========================================
+ Hits        78772    78799      +27     
- Misses      52107    52126      +19     
  Partials      908      908

Flag	Coverage Δ
apps.hash-ai-worker-ts	`1.39% <ø> (-0.01%)`	⬇️
apps.hash-api	`3.26% <ø> (ø)`
blockprotocol.type-system	`40.84% <ø> (ø)`
local.claude-hooks	`0.00% <ø> (ø)`
local.harpc-client	`51.49% <ø> (ø)`
local.hash-backend-utils	`2.81% <ø> (ø)`
local.hash-graph-sdk	`9.63% <ø> (ø)`
local.hash-isomorphic-utils	`0.18% <ø> (-0.01%)`	⬇️
rust.antsi	`0.00% <ø> (ø)`
rust.error-stack	`90.87% <ø> (ø)`
rust.harpc-codec	`84.70% <ø> (ø)`
rust.harpc-net	`96.19% <ø> (ø)`
rust.harpc-tower	`67.03% <ø> (ø)`
rust.harpc-types	`0.00% <ø> (ø)`
rust.harpc-wire-protocol	`92.23% <ø> (ø)`
rust.hash-codec	`72.76% <ø> (ø)`
rust.hash-graph-api	`2.53% <ø> (ø)`
rust.hash-graph-authorization	`62.59% <ø> (+0.18%)`	⬆️
rust.hash-graph-store	`37.90% <ø> (-0.10%)`	⬇️
rust.hash-graph-temporal-versioning	`47.95% <ø> (ø)`
rust.hash-graph-types	`0.00% <ø> (ø)`
rust.hash-graph-validation	`83.43% <ø> (ø)`
rust.hashql-ast	`87.23% <ø> (ø)`
rust.hashql-compiletest	`28.24% <ø> (ø)`
rust.hashql-core	`79.60% <ø> (ø)`
rust.hashql-diagnostics	`72.31% <ø> (ø)`
rust.hashql-eval	`75.23% <ø> (ø)`
rust.hashql-hir	`89.06% <ø> (ø)`
rust.hashql-mir	`88.45% <ø> (ø)`
rust.hashql-syntax-jexpr	`94.04% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

cursor · 2026-01-12T11:45:06Z

PR Summary

Medium Risk
Telemetry/OTLP export and tracing–OpenTelemetry bridging can change behavior across upstream breaking releases, and the repo temporarily mixes opentelemetry_sdk 0.30 (direct) with 0.32 (transitive), which warrants validation of OTLP traces/logs/metrics in deployed environments.

Overview
Renovate bumps the workspace OpenTelemetry stack in root Cargo.toml: opentelemetry, opentelemetry-appender-tracing, opentelemetry-otlp, and opentelemetry-semantic-conventions from 0.30.x → 0.32.0, and tracing-opentelemetry from 0.31.0 → 0.33.0. opentelemetry_sdk stays pinned at 0.30.0 in the workspace while Cargo.lock also pulls 0.32.1 for the upgraded OTLP/proto path.

The lockfile refresh drops older duplicate stacks (tonic 0.13, prost 0.13, older opentelemetry-otlp), standardizes on tonic 0.14 / prost 0.14, and adjusts several transitive pins (e.g. windows-sys, spin). No application Rust source changes—only dependency manifests.

^{Reviewed by Cursor Bugbot for commit 5149cd2. Bugbot is set up for automated code reviews on this repo. Configure here.}

codspeed-hq · 2026-01-22T12:58:39Z

Merging this PR will degrade performance by 15.38%

⚠️

Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 2 regressed benchmarks
✅ 78 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	`BASE`	`HEAD`	Efficiency
❌	`bit_matrix/dense/iter_row[64]`	140.8 ns	170 ns	-17.16%
❌	`bit_matrix/dense/iter_row[200]`	185.8 ns	215 ns	-13.57%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

_{Comparing deps/rs/opentelemetry-rust-crates (5149cd2) with main (b8f5e58)}

cursor · 2026-04-29T11:47:36Z

 "tokio-util",
 "tracing",
- "tracing-opentelemetry",
+ "tracing-opentelemetry 0.31.0",


Duplicate OpenTelemetry versions break tarpc trace propagation

Medium Severity

The tarpc git dependency is pinned to opentelemetry 0.30.0 and tracing-opentelemetry 0.31.0, while the workspace now uses opentelemetry 0.31.0 and tracing-opentelemetry 0.32.1. Before this PR, all crates shared a single version. Now, two incompatible versions of tracing-opentelemetry coexist in the binary. Since OpenTelemetrySpanExt methods interact with span extension data (OtelData) by TypeId, tarpc's version 0.31.0 OtelData won't match the application layer's version 0.32.1 OtelData. This silently breaks trace context propagation across tarpc RPC calls used by the type fetcher service.

Additional Locations (1)

Cargo.lock#L9761-L9790

^{Reviewed by Cursor Bugbot for commit 5ad55e9. Configure here.}

cursor · 2026-05-12T17:03:22Z

+opentelemetry-appender-tracing     = { version = "0.31.0", default-features = false }
+opentelemetry-otlp                 = { version = "0.31.0", default-features = false }
+opentelemetry-semantic-conventions = { version = "0.31.0", default-features = false }
+opentelemetry_sdk                  = { version = "0.31.0", default-features = false }


OpenTelemetry version split breaks tarpc trace context propagation

Medium Severity

Updating the workspace opentelemetry to 0.31.0 and tracing-opentelemetry to 0.32.x introduces a version split because tarpc (pinned to a git revision) still depends on opentelemetry 0.30.0 and tracing-opentelemetry 0.31.0. Before this PR, all crates shared the same OpenTelemetry versions. Now two separate opentelemetry::global states exist — the app configures the 0.31.0 global (propagator, tracer provider), but tarpc operates on the unconfigured 0.30.0 global. Additionally, the tracing-opentelemetry 0.32.1 layer stores span extension data as its own types, which tarpc's 0.31.0 OpenTelemetrySpanExt calls can't retrieve. This silently breaks trace context propagation across tarpc RPC boundaries (the type-fetcher service).

Additional Locations (1)

Cargo.lock#L9038-L9051

^{Reviewed by Cursor Bugbot for commit 728c751. Configure here.}

github-actions · 2026-06-24T11:14:22Z

Benchmark results

@rust/hash-graph-benches – Integrations

policy_resolution_large

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 2002	$$26.1 \mathrm{ms} \pm 138 \mathrm{μs}\left({\color{gray}-2.576 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$3.60 \mathrm{ms} \pm 25.0 \mathrm{μs}\left({\color{gray}0.831 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 1001	$$13.7 \mathrm{ms} \pm 90.4 \mathrm{μs}\left({\color{gray}0.311 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: high, policies: 3314	$$44.3 \mathrm{ms} \pm 357 \mathrm{μs}\left({\color{gray}-0.228 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: low, policies: 1	$$16.4 \mathrm{ms} \pm 148 \mathrm{μs}\left({\color{gray}1.42 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: medium, policies: 1526	$$25.7 \mathrm{ms} \pm 194 \mathrm{μs}\left({\color{gray}2.19 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 2078	$$27.5 \mathrm{ms} \pm 178 \mathrm{μs}\left({\color{gray}-0.284 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$3.95 \mathrm{ms} \pm 22.2 \mathrm{μs}\left({\color{gray}-0.005 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 1033	$$14.6 \mathrm{ms} \pm 106 \mathrm{μs}\left({\color{gray}0.041 \mathrm{\%}}\right) $$	Flame Graph

policy_resolution_medium

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 102	$$3.82 \mathrm{ms} \pm 28.8 \mathrm{μs}\left({\color{gray}3.67 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$3.04 \mathrm{ms} \pm 14.9 \mathrm{μs}\left({\color{gray}0.675 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 51	$$3.39 \mathrm{ms} \pm 19.5 \mathrm{μs}\left({\color{gray}0.024 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: high, policies: 269	$$5.23 \mathrm{ms} \pm 30.1 \mathrm{μs}\left({\color{gray}1.69 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: low, policies: 1	$$3.61 \mathrm{ms} \pm 16.8 \mathrm{μs}\left({\color{gray}0.234 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: medium, policies: 107	$$4.19 \mathrm{ms} \pm 25.0 \mathrm{μs}\left({\color{gray}1.32 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 133	$$4.44 \mathrm{ms} \pm 33.4 \mathrm{μs}\left({\color{gray}2.64 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$3.53 \mathrm{ms} \pm 19.2 \mathrm{μs}\left({\color{gray}1.34 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 63	$$4.16 \mathrm{ms} \pm 31.1 \mathrm{μs}\left({\color{gray}1.67 \mathrm{\%}}\right) $$	Flame Graph

policy_resolution_none

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 2	$$2.61 \mathrm{ms} \pm 16.3 \mathrm{μs}\left({\color{gray}-0.261 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$2.54 \mathrm{ms} \pm 11.9 \mathrm{μs}\left({\color{gray}-0.708 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 1	$$2.63 \mathrm{ms} \pm 13.1 \mathrm{μs}\left({\color{gray}0.633 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 8	$$2.87 \mathrm{ms} \pm 18.0 \mathrm{μs}\left({\color{gray}0.887 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$2.69 \mathrm{ms} \pm 18.4 \mathrm{μs}\left({\color{gray}1.85 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 3	$$2.87 \mathrm{ms} \pm 16.9 \mathrm{μs}\left({\color{gray}0.301 \mathrm{\%}}\right) $$	Flame Graph

policy_resolution_small

Function	Value	Mean	Flame graphs
resolve_policies_for_actor	user: empty, selectivity: high, policies: 52	$$3.03 \mathrm{ms} \pm 15.1 \mathrm{μs}\left({\color{gray}0.436 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: low, policies: 1	$$2.81 \mathrm{ms} \pm 16.0 \mathrm{μs}\left({\color{gray}1.75 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: empty, selectivity: medium, policies: 25	$$3.03 \mathrm{ms} \pm 17.8 \mathrm{μs}\left({\color{gray}1.14 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: high, policies: 94	$$3.48 \mathrm{ms} \pm 22.8 \mathrm{μs}\left({\color{gray}1.76 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: low, policies: 1	$$3.06 \mathrm{ms} \pm 19.5 \mathrm{μs}\left({\color{gray}3.00 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: seeded, selectivity: medium, policies: 26	$$3.38 \mathrm{ms} \pm 25.3 \mathrm{μs}\left({\color{gray}2.66 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: high, policies: 66	$$3.36 \mathrm{ms} \pm 22.5 \mathrm{μs}\left({\color{gray}0.521 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: low, policies: 1	$$2.99 \mathrm{ms} \pm 13.6 \mathrm{μs}\left({\color{gray}0.207 \mathrm{\%}}\right) $$	Flame Graph
resolve_policies_for_actor	user: system, selectivity: medium, policies: 29	$$3.33 \mathrm{ms} \pm 21.5 \mathrm{μs}\left({\color{gray}-0.222 \mathrm{\%}}\right) $$	Flame Graph

read_scaling_complete

Function	Value	Mean	Flame graphs
entity_by_id;one_depth	1 entities	$$43.9 \mathrm{ms} \pm 225 \mathrm{μs}\left({\color{gray}4.66 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	10 entities	$$33.7 \mathrm{ms} \pm 156 \mathrm{μs}\left({\color{gray}0.779 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	25 entities	$$37.7 \mathrm{ms} \pm 191 \mathrm{μs}\left({\color{gray}4.07 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	5 entities	$$32.8 \mathrm{ms} \pm 193 \mathrm{μs}\left({\color{gray}4.17 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;one_depth	50 entities	$$44.4 \mathrm{ms} \pm 319 \mathrm{μs}\left({\color{gray}3.22 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	1 entities	$$52.3 \mathrm{ms} \pm 342 \mathrm{μs}\left({\color{gray}4.47 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	10 entities	$$40.9 \mathrm{ms} \pm 195 \mathrm{μs}\left({\color{gray}0.760 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	25 entities	$$95.7 \mathrm{ms} \pm 390 \mathrm{μs}\left({\color{gray}2.30 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	5 entities	$$34.7 \mathrm{ms} \pm 177 \mathrm{μs}\left({\color{gray}3.20 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;two_depth	50 entities	$$278 \mathrm{ms} \pm 1.09 \mathrm{ms}\left({\color{lightgreen}-9.592 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	1 entities	$$10.5 \mathrm{ms} \pm 64.1 \mathrm{μs}\left({\color{gray}0.161 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	10 entities	$$10.6 \mathrm{ms} \pm 58.0 \mathrm{μs}\left({\color{gray}-1.212 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	25 entities	$$10.8 \mathrm{ms} \pm 52.7 \mathrm{μs}\left({\color{gray}0.562 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	5 entities	$$10.4 \mathrm{ms} \pm 52.6 \mathrm{μs}\left({\color{gray}-0.877 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id;zero_depth	50 entities	$$10.7 \mathrm{ms} \pm 72.6 \mathrm{μs}\left({\color{gray}1.63 \mathrm{\%}}\right) $$	Flame Graph

read_scaling_linkless

Function	Value	Mean	Flame graphs
entity_by_id	1 entities	$$10.6 \mathrm{ms} \pm 63.2 \mathrm{μs}\left({\color{gray}3.24 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10 entities	$$10.5 \mathrm{ms} \pm 57.2 \mathrm{μs}\left({\color{gray}1.20 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	100 entities	$$10.4 \mathrm{ms} \pm 51.0 \mathrm{μs}\left({\color{gray}-0.889 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	1000 entities	$$10.8 \mathrm{ms} \pm 67.8 \mathrm{μs}\left({\color{gray}1.24 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	10000 entities	$$10.8 \mathrm{ms} \pm 58.8 \mathrm{μs}\left({\color{gray}-2.163 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity

Function	Value	Mean	Flame graphs
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/block/v/1`	$$11.0 \mathrm{ms} \pm 57.9 \mathrm{μs}\left({\color{gray}-0.062 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/book/v/1`	$$11.0 \mathrm{ms} \pm 63.1 \mathrm{μs}\left({\color{gray}0.839 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/building/v/1`	$$11.2 \mathrm{ms} \pm 81.0 \mathrm{μs}\left({\color{gray}2.83 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/organization/v/1`	$$11.2 \mathrm{ms} \pm 82.2 \mathrm{μs}\left({\color{gray}0.938 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/page/v/2`	$$11.1 \mathrm{ms} \pm 47.7 \mathrm{μs}\left({\color{gray}1.68 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/person/v/1`	$$11.7 \mathrm{ms} \pm 81.2 \mathrm{μs}\left({\color{red}5.90 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/playlist/v/1`	$$10.9 \mathrm{ms} \pm 62.0 \mathrm{μs}\left({\color{gray}0.361 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/song/v/1`	$$11.2 \mathrm{ms} \pm 78.9 \mathrm{μs}\left({\color{gray}1.09 \mathrm{\%}}\right) $$	Flame Graph
entity_by_id	entity type ID: `https://blockprotocol.org/@alice/types/entity-type/uk-address/v/1`	$$10.9 \mathrm{ms} \pm 77.1 \mathrm{μs}\left({\color{gray}0.733 \mathrm{\%}}\right) $$	Flame Graph

representative_read_entity_type

Function	Value	Mean	Flame graphs
get_entity_type_by_id	Account ID: `bf5a9ef5-dc3b-43cf-a291-6210c0321eba`	$$9.05 \mathrm{ms} \pm 61.3 \mathrm{μs}\left({\color{red}7.31 \mathrm{\%}}\right) $$	Flame Graph

representative_read_multiple_entities

Function	Value	Mean	Flame graphs
entity_by_property	traversal_paths=0	0	$$63.1 \mathrm{ms} \pm 416 \mathrm{μs}\left({\color{red}8.95 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=255	1,resolve_depths=inherit:1;values:255;properties:255;links:127;link_dests:126;type:true	$$110 \mathrm{ms} \pm 687 \mathrm{μs}\left({\color{gray}0.874 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:0;link_dests:0;type:false	$$66.7 \mathrm{ms} \pm 556 \mathrm{μs}\left({\color{red}6.27 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:1;link_dests:0;type:true	$$75.4 \mathrm{ms} \pm 580 \mathrm{μs}\left({\color{gray}3.53 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:2;links:1;link_dests:0;type:true	$$84.9 \mathrm{ms} \pm 474 \mathrm{μs}\left({\color{gray}4.03 \mathrm{\%}}\right) $$
entity_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:2;properties:2;links:1;link_dests:0;type:true	$$88.0 \mathrm{ms} \pm 484 \mathrm{μs}\left({\color{gray}-2.549 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=0	0	$$46.4 \mathrm{ms} \pm 308 \mathrm{μs}\left({\color{gray}2.03 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=255	1,resolve_depths=inherit:1;values:255;properties:255;links:127;link_dests:126;type:true	$$75.5 \mathrm{ms} \pm 307 \mathrm{μs}\left({\color{gray}-2.390 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:0;link_dests:0;type:false	$$54.2 \mathrm{ms} \pm 311 \mathrm{μs}\left({\color{gray}-0.106 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:0;links:1;link_dests:0;type:true	$$62.5 \mathrm{ms} \pm 304 \mathrm{μs}\left({\color{gray}-2.477 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:0;properties:2;links:1;link_dests:0;type:true	$$65.8 \mathrm{ms} \pm 482 \mathrm{μs}\left({\color{gray}-1.315 \mathrm{\%}}\right) $$
link_by_source_by_property	traversal_paths=2	1,resolve_depths=inherit:0;values:2;properties:2;links:1;link_dests:0;type:true	$$65.2 \mathrm{ms} \pm 300 \mathrm{μs}\left({\color{gray}-1.031 \mathrm{\%}}\right) $$

scenarios

Function	Value	Mean	Flame graphs
full_test	query-limited	$$122 \mathrm{ms} \pm 465 \mathrm{μs}\left({\color{red}5.49 \mathrm{\%}}\right) $$	Flame Graph
full_test	query-unlimited	$$133 \mathrm{ms} \pm 405 \mathrm{μs}\left({\color{gray}4.43 \mathrm{\%}}\right) $$	Flame Graph
linked_queries	query-limited	$$19.1 \mathrm{ms} \pm 138 \mathrm{μs}\left({\color{gray}2.71 \mathrm{\%}}\right) $$	Flame Graph
linked_queries	query-unlimited	$$547 \mathrm{ms} \pm 1.06 \mathrm{ms}\left({\color{gray}-3.224 \mathrm{\%}}\right) $$	Flame Graph

hash-worker · 2026-06-28T01:23:26Z

⚠️ Artifact update problem

Renovate failed to update an artifact 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.toml

Artifact update for opentelemetry-semantic-conventions resolved to version 0.32.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.32.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 4 total unresolved issues (including 3 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 5149cd2. Configure here.}

cursor · 2026-06-28T01:24:37Z

+opentelemetry                      = { version = "0.32.0", default-features = false }
+opentelemetry-appender-tracing     = { version = "0.32.0", default-features = false }
+opentelemetry-otlp                 = { version = "0.32.0", default-features = false }
+opentelemetry-semantic-conventions = { version = "0.32.0", default-features = false }


SDK left on 0.30

High Severity

The workspace bumps opentelemetry, opentelemetry-otlp, and tracing-opentelemetry to 0.32/0.33 but leaves opentelemetry_sdk at 0.30.0. OTLP 0.32 is built against opentelemetry_sdk 0.32.x, while hash-telemetry builds providers from workspace SDK 0.30, so exporters and providers no longer share one SDK version.

Additional Locations (1)

Cargo.lock#L3989-L3990

^{Reviewed by Cursor Bugbot for commit 5149cd2. Configure here.}

hash-worker Bot enabled auto-merge November 5, 2025 00:34

hash-worker Bot assigned indietyp and TimDiekmann Nov 5, 2025

hash-worker Bot requested a review from a team November 5, 2025 00:34

github-actions Bot added the area/deps Relates to third-party dependencies (area) label Nov 5, 2025

vercel Bot deployed to Preview – hashdotdesign November 5, 2025 00:37 View deployment

vercel Bot deployed to Preview – hash November 5, 2025 00:47 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 2ab7c86 to 3750c33 Compare November 19, 2025 13:50

vercel Bot had a problem deploying to Preview – petrinaut November 19, 2025 13:51 Failure

vercel Bot deployed to Preview – hashdotdesign November 19, 2025 13:53 View deployment

vercel Bot deployed to Preview – hash November 19, 2025 14:03 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 3750c33 to 22383b2 Compare December 7, 2025 09:42

vercel Bot deployed to Preview – hashdotdesign December 7, 2025 09:46 View deployment

vercel Bot deployed to Preview – petrinaut December 7, 2025 09:47 View deployment

vercel Bot deployed to Preview – hash December 7, 2025 09:55 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 22383b2 to 56681d9 Compare January 12, 2026 11:45

vercel Bot deployed to Preview – hashdotdesign January 12, 2026 11:48 View deployment

vercel Bot deployed to Preview – petrinaut January 12, 2026 11:50 View deployment

vercel Bot deployed to Preview – hash January 12, 2026 11:59 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 56681d9 to 1574cf8 Compare January 22, 2026 12:54

vercel Bot deployed to Preview – ds-theme January 22, 2026 12:57 View deployment

vercel Bot deployed to Preview – hashdotdesign January 22, 2026 12:57 View deployment

vercel Bot deployed to Preview – petrinaut January 22, 2026 12:58 View deployment

vercel Bot deployed to Preview – hash January 22, 2026 13:07 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 1574cf8 to 296ff99 Compare February 17, 2026 09:26

vercel Bot deployed to Preview – hashdotdesign-tokens February 17, 2026 09:29 View deployment

cursor Bot reviewed Apr 29, 2026

View reviewed changes

vercel Bot deployed to Preview – hash April 29, 2026 11:55 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 5ad55e9 to 13a7a31 Compare May 5, 2026 11:09

vercel Bot deployed to Preview – hashdotdesign-tokens May 5, 2026 11:12 View deployment

vercel Bot deployed to Preview – petrinaut May 5, 2026 11:13 View deployment

vercel Bot deployed to Preview – hash May 5, 2026 11:22 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 13a7a31 to 728c751 Compare May 12, 2026 16:57

vercel Bot deployed to Preview – hashdotdesign-tokens May 12, 2026 17:00 View deployment

vercel Bot deployed to Preview – petrinaut May 12, 2026 17:01 View deployment

cursor Bot reviewed May 12, 2026

View reviewed changes

vercel Bot deployed to Preview – hash May 12, 2026 17:13 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 728c751 to 3931625 Compare May 23, 2026 01:09

hash-worker Bot changed the title ~~Update opentelemetry Rust crates~~ Update opentelemetry Rust crates to 0.32.0 May 23, 2026

vercel Bot deployed to Preview – hashdotdesign-tokens May 23, 2026 01:12 View deployment

vercel Bot deployed to Preview – petrinaut May 23, 2026 01:13 View deployment

cursor Bot reviewed May 23, 2026

View reviewed changes

Comment thread Cargo.toml Outdated

vercel Bot had a problem deploying to Preview – hash May 23, 2026 01:16 Failure

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 3931625 to 2abf415 Compare June 1, 2026 23:16

hash-worker Bot changed the title ~~Update opentelemetry Rust crates to 0.32.0~~ Update opentelemetry Rust crates Jun 1, 2026

vercel Bot deployed to Preview – hashdotdesign-tokens June 1, 2026 23:18 View deployment

vercel Bot deployed to Preview – petrinaut June 1, 2026 23:21 View deployment

vercel Bot deployed to Preview – hash June 1, 2026 23:28 View deployment

hash-worker Bot force-pushed the deps/rs/opentelemetry-rust-crates branch from 2abf415 to f0d187e Compare June 9, 2026 17:08

vercel Bot deployed to Preview – hashdotdesign-tokens June 9, 2026 17:11 View deployment

vercel Bot deployed to Preview – petrinaut June 9, 2026 17:13 View deployment

vercel Bot deployed to Preview – hash June 9, 2026 17:21 View deployment

Update opentelemetry Rust crates

5149cd2

cursor Bot reviewed Jun 28, 2026

View reviewed changes

Uh oh!

Conversation

hash-worker Bot commented Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v0.31.1: opentelemetry-otlp 0.31.1

What's Changed

Fixed

Other

Added

Fixed

Other

Added

Changed

Breaking Changes

Configuration

Uh oh!

vercel Bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

cursor Bot commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

codspeed-hq Bot commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merging this PR will degrade performance by 15.38%

Performance Changes

Uh oh!

cursor Bot Apr 29, 2026

Choose a reason for hiding this comment

Duplicate OpenTelemetry versions break tarpc trace propagation

Uh oh!

cursor Bot May 12, 2026

Choose a reason for hiding this comment

OpenTelemetry version split breaks tarpc trace context propagation

Uh oh!

Uh oh!

github-actions Bot commented Jun 24, 2026

Benchmark results

@rust/hash-graph-benches – Integrations

policy_resolution_large

policy_resolution_medium

policy_resolution_none

policy_resolution_small

read_scaling_complete

read_scaling_linkless

representative_read_entity

representative_read_entity_type

representative_read_multiple_entities

scenarios

Uh oh!

hash-worker Bot commented Jun 28, 2026

⚠️ Artifact update problem

File name: Cargo.toml

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Jun 28, 2026

Choose a reason for hiding this comment

SDK left on 0.30

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

2 participants

hash-worker Bot commented Nov 5, 2025 •

edited

Loading

`v0.31.1`: opentelemetry-otlp 0.31.1

vercel Bot commented Nov 19, 2025 •

edited

Loading

codecov Bot commented Nov 19, 2025 •

edited

Loading

cursor Bot commented Jan 12, 2026 •

edited

Loading

codspeed-hq Bot commented Jan 22, 2026 •

edited

Loading