Update Rust crate temporalio-client to 9f83b7e

[hash-worker]

This PR contains the following updates:

Package	Type	Update	Change
temporalio-client	workspace.dependencies	digest	231e21c → 9f83b7e

---

Warning

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

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Renovate Bot.

[cursor]

PR Summary

Medium Risk
A large semver-style SDK bump (0.5) affects workflow gRPC client behavior used by hash-temporal-client, and the split pin on temporalio-common may hide API/proto mismatches until compile or runtime.

Overview
Renovate bumps the workspace temporalio-client git dependency from 231e21c to 9f83b7e, with Cargo.lock reflecting a 0.1.0 → 0.5.0 SDK jump.

The resolved client now pulls temporalio-common 0.5.0, temporalio-protos, and tokio-rustls, and drops slotmap from the client dependency tree; several transitive crates (dirs, flate2, pbjson, etc.) appear as a result. Workspace temporalio-common remains pinned to 231e21c, so the lockfile currently carries two temporalio-common versions—the new one via temporalio-client and 0.1.0 for direct hash-temporal-client use.

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
hash	Error		Jul 2, 2026 4:54pm
hashdotdesign	Ready	Preview, Comment	Jul 2, 2026 4:54pm
hashdotdesign-tokens	Ready	Preview, Comment	Jul 2, 2026 4:54pm
petrinaut	Ready	Preview	Jul 2, 2026 4:54pm

[cursor]

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

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates the Rust dependency on temporalio-client to a newer git revision.

Changes:

• Bumps temporalio-client from rev 231e21c to 7ecb7c0… (from the Temporal sdk-core repo)
• Regenerates Cargo.lock to reflect the updated dependency graph

Technical Notes: Only the temporalio-client git rev is changed; other Temporal crates (e.g., temporalio-common) remain pinned to their prior rev.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

temporalio-client is bumped to a newer sdk-core revision, but temporalio-common is still pinned to the older 231e21c rev. Since both come from the same upstream repo, it’s worth double-checking that this mixed-rev combination is intentional/compatible (otherwise consider updating them in lockstep).

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.61%. Comparing base (98dd31f) to head (08c770e).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8415   +/-   ##
=======================================
  Coverage   59.61%   59.61%           
=======================================
  Files        1366     1366           
  Lines      132649   132687   +38     
  Branches     6044     6044           
=======================================
+ Hits        79078    79105   +27     
- Misses      52637    52648   +11     
  Partials      934      934           

Flag	Coverage Δ
local.claude-hooks	0.00% <ø> (ø)
local.harpc-client	51.49% <ø> (ø)
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-authorization	62.59% <ø> (+0.18%)	⬆️
rust.hash-graph-temporal-versioning	47.95% <ø> (ø)
rust.hashql-core	79.58% <ø> (-0.03%)	⬇️
rust.hashql-diagnostics	72.31% <ø> (ø)
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.

[codspeed-hq]

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
✅ 54 untouched benchmarks
⏩ 24 skipped 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/temporalio-client-digest (08c770e) with main (98dd31f)²}

Footnotes

1. 24 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (a07be79) during the generation of this report, so 98dd31f was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[claude]

🔴 Only temporalio-client was bumped to rev 9f83b7e (v0.5.0); temporalio-common on the next line is still pinned to rev 231e21c (v0.1.0). Because both crates come from the same sdk-core monorepo and libs/@local/temporal-client/src/ai.rs imports proto types from temporalio_common v0.1.0 while calling WorkflowService::start_workflow_execution from temporalio_client v0.5.0, the workspace no longer compiles — Cargo.lock now contains two coexisting versions of temporalio-common and Rust treats types across the two revs as distinct. Fix by bumping temporalio-common on line 259 to the same rev (9f83b7e307dc032b31ff3bd3811ef3438106f77a) and regenerating the lockfile.

Extended reasoning...

The bug

The workspace declaration in Cargo.toml pins both temporalio-client and temporalio-common to git revisions from the same upstream repo (github.com/temporalio/sdk-core). This PR bumps only the client:

temporalio-client = { git = "https://github.com/temporalio/sdk-core", rev = "9f83b7e307dc032b31ff3bd3811ef3438106f77a" }  # v0.5.0
temporalio-common = { git = "https://github.com/temporalio/sdk-core", rev = "231e21c" }                                  # v0.1.0

The updated Cargo.lock confirms the split — two distinct temporalio-common packages coexist (0.1.0 at 231e21c and 0.5.0 at 9f83b7e), and hash-temporal-client still depends on the old temporalio-common 0.1.0 while the bumped temporalio-client 0.5.0 transitively pulls in temporalio-common 0.5.0.

Why this breaks compilation

libs/@local/temporal-client/src/ai.rs mixes the two:

// line 6 — resolves to temporalio_client 0.5.0
use temporalio_client::{NamespacedClient, WorkflowService, tonic::IntoRequest as _};
// lines 7-16 — resolves to temporalio_common 0.1.0 (per workspace pin)
use temporalio_common::protos::{
    ENCODING_PAYLOAD_KEY, JSON_ENCODING_VAL,
    coresdk::IntoPayloadsExt as _,
    temporal::api::{
        common::v1::{Header, Payload, WorkflowType},
        enums::v1::TaskQueueKind,
        taskqueue::v1::TaskQueue,
        workflowservice::v1::StartWorkflowExecutionRequest,
    },
};

Rust nominal typing treats items from two different git revisions of the same crate as distinct types, even when the source is byte-identical. So StartWorkflowExecutionRequest from temporalio_common@0.1.0 is a different type than StartWorkflowExecutionRequest from temporalio_common@0.5.0 (which temporalio_client@0.5.0 now expects internally).

Step-by-step proof

1. ai.rs builds a StartWorkflowExecutionRequest using types imported from temporalio_common — the workspace resolves this to v0.1.0 (rev 231e21c).
2. That request is handed to WorkflowService::start_workflow_execution(...) — a tonic-generated method on temporalio_client v0.5.0, whose signature is fn start_workflow_execution<R: IntoRequest<StartWorkflowExecutionRequest_v0_5_0>>(...).
3. Tonic's blanket IntoRequest impl only exists for the request type from temporalio_common@0.5.0 (the one temporalio_client v0.5.0 was compiled against).
4. The compiler tries to unify StartWorkflowExecutionRequest_v0_1_0 with StartWorkflowExecutionRequest_v0_5_0 and fails with an E0308 mismatch on the IntoRequest trait bound.

Blast radius

hash-temporal-client is a direct dep of hash-graph (the default workspace member) and of libs/@local/graph/{api,store,postgres-store,type-fetcher}, so the whole workspace fails to build.

Fix

Bump line 259 in Cargo.toml to the same rev as the client and regenerate the lockfile:

temporalio-common = { git = "https://github.com/temporalio/sdk-core", rev = "9f83b7e307dc032b31ff3bd3811ef3438106f77a" }

After regeneration only one version of temporalio-common should remain in Cargo.lock, and hash-temporal-client will depend on the same rev that temporalio-client was compiled against. Both the cursor bot and augmentcode bot flagged this on the PR as well.

_{🔬 also observed by cursor}