Update Rust crate temporalio-common to c09a290

[hash-worker]

This PR contains the following updates:

Package	Type	Update	Change
temporalio-common	workspace.dependencies	digest	231e21c -> c09a290

---

Warning

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

---

Configuration

📅 Schedule: Branch creation - "before 4am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 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		Feb 26, 2026 6:04pm
hashdotdesign	Ready	Preview, Comment	Feb 26, 2026 6:04pm
hashdotdesign-tokens	Ready	Preview, Comment	Feb 26, 2026 6:04pm
petrinaut	Ready	Preview	Feb 26, 2026 6:04pm

[cursor]

PR Summary

Medium Risk
Updates a core Temporal SDK dependency to a new git revision, pulling in additional transitive crates and potentially changing runtime/serialization behavior used by Temporal clients.

Overview
Bumps the workspace temporalio-common git dependency from 231e21c to c09a29014c257f932e40c20db955efe0bea45baa (while leaving temporalio-client pinned to 231e21c).

Regenerates Cargo.lock, introducing new transitive dependencies for temporalio-common (notably pbjson* and related protobuf/serde helpers) and adjusting dependent lock entries (e.g., hash-temporal-client, tracing-subscriber).

^{Written by Cursor Bugbot for commit b191eea. This will update automatically on new commits. 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 62.70%. Comparing base (e7770d8) to head (b191eea).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8421      +/-   ##
==========================================
- Coverage   62.70%   62.70%   -0.01%     
==========================================
  Files        1302     1302              
  Lines      131589   131595       +6     
  Branches     5487     5487              
==========================================
  Hits        82512    82512              
- Misses      48169    48175       +6     
  Partials      908      908              

Flag	Coverage Δ
local.claude-hooks	0.00% <ø> (ø)
local.harpc-client	51.24% <ø> (ø)
rust.antsi	0.00% <ø> (ø)
rust.error-stack	90.88% <ø> (ø)
rust.harpc-codec	84.70% <ø> (ø)
rust.harpc-net	96.16% <ø> (ø)
rust.harpc-tower	66.80% <ø> (ø)
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	82.26% <ø> (-0.03%)	⬇️
rust.hashql-diagnostics	72.43% <ø> (ø)
rust.hashql-syntax-jexpr	94.05% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 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 not alter performance

✅ 44 untouched benchmarks
⏩ 24 skipped benchmarks¹
🗄️ 12 archived benchmarks run²

---

_{Comparing deps/rs/temporalio-common-digest (b191eea) with main (e957752)}

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. 12 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩

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

[cursor]

Temporal SDK revisions are now inconsistent

Medium Severity

temporalio-client stays on rev 231e21c while temporalio-common is bumped to 12c656f..., so the workspace now resolves two different temporalio-common crates. This can break interoperability where hash-temporal-client uses both crates, because shared SDK types may no longer be identical across crate boundaries.

Additional Locations (1)

• Cargo.lock#L8810-L8824