Update Rust crate temporalio-common to 286baac

[hash-worker]

This PR contains the following updates:

Package	Type	Update	Change
temporalio-common	workspace.dependencies	digest	231e21c → 286baac

---

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.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
hash	Error		Jun 24, 2026 9:18pm
hashdotdesign	Ready	Preview, Comment	Jun 24, 2026 9:18pm
hashdotdesign-tokens	Ready	Preview, Comment	Jun 24, 2026 9:18pm
petrinaut	Ready	Preview	Jun 24, 2026 9:18pm

[cursor]

PR Summary

Medium Risk
Dependency-only change in workflow client code, but it splits Temporal SDK revisions and may surface API or proto mismatches between temporalio-client and the newer temporalio-common.

Overview
Bumps the workspace temporalio-common git dependency from 231e21c to 286baac, with Cargo.lock reflecting 0.4.0 (and new sdk-core crates such as temporalio-protos, temporalio-common-wasm, and pbjson).

hash-temporal-client is the direct consumer of this workspace pin. temporalio-client stays on 231e21c, so the lockfile now carries two temporalio-common versions (0.1.0 for the client crate, 0.4.0 for the workspace pin)—worth a quick compile/integration pass on Temporal usage.

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

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates the pinned git revision for the Rust crate temporalio-common.

Changes:

• Bumps temporalio-common from SDK Core rev 231e21c to fb14d9c3 in the workspace dependencies
• Leaves temporalio-client pinned to the prior revision
• Updates the lockfile accordingly (Cargo.lock)

Technical Notes: Since both crates come from the same upstream repository, mixing revisions may result in multiple git checkouts/duplicate crate versions unless they are intentionally kept independent.

_{🤖 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-common is now pinned to a different git rev than temporalio-client (same upstream repo), which can cause Cargo to pull two distinct copies and potentially lead to type/version mismatches. Is it expected that these two crates are compatible across different commits, or should they be bumped together to the same rev?

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 (fd129ea) to head (cfd9c02).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8421      +/-   ##
==========================================
- Coverage   59.61%   59.61%   -0.01%     
==========================================
  Files        1348     1348              
  Lines      131877   131877              
  Branches     5944     5944              
==========================================
- Hits        78615    78614       -1     
- Misses      52357    52358       +1     
  Partials      905      905              

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% <ø> (-0.02%)	⬇️
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.34% <ø> (ø)
rust.hash-graph-temporal-versioning	47.95% <ø> (ø)
rust.hashql-core	79.60% <ø> (ø)
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-common-digest (cfd9c02) with main (3dbbe7b)²}

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 (0eea201) during the generation of this report, so 3dbbe7b was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[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.}