Skip to content

Update Rust crate scc to v3#8131

Open
hash-worker[bot] wants to merge 1 commit into
mainfrom
deps/rs/scc-3.x
Open

Update Rust crate scc to v3#8131
hash-worker[bot] wants to merge 1 commit into
mainfrom
deps/rs/scc-3.x

Conversation

@hash-worker

@hash-worker hash-worker Bot commented Nov 30, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Pending
scc workspace.dependencies major 2.4.03.0.0 3.8.3 (+3)

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.

@hash-worker hash-worker Bot enabled auto-merge November 30, 2025 15:14
@github-actions github-actions Bot added the area/deps Relates to third-party dependencies (area) label Nov 30, 2025
@hash-worker hash-worker Bot requested a review from a team November 30, 2025 15:44
@codecov

codecov Bot commented Dec 9, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.61%. Comparing base (fd129ea) to head (65ddeaf).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8131   +/-   ##
=======================================
  Coverage   59.61%   59.61%           
=======================================
  Files        1348     1348           
  Lines      131877   131877           
  Branches     5944     5944           
=======================================
  Hits        78615    78615           
  Misses      52357    52357           
  Partials      905      905           
Flag Coverage Δ
apps.hash-ai-worker-ts 1.39% <ø> (ø)
apps.hash-api 0.00% <ø> (ø)
blockprotocol.type-system 40.84% <ø> (ø)
local.claude-hooks 0.00% <ø> (ø)
local.harpc-client 51.49% <ø> (ø)
local.hash-backend-utils 2.82% <ø> (ø)
local.hash-graph-sdk 9.63% <ø> (ø)
local.hash-isomorphic-utils 0.00% <ø> (ø)
rust.antsi 0.00% <ø> (ø)
rust.error-stack 90.87% <ø> (ø)
rust.harpc-codec 84.70% <ø> (ø)
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-postgres-store 29.02% <ø> (ø)
rust.hash-graph-store 37.99% <ø> (ø)
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

cursor Bot commented Dec 16, 2025

Copy link
Copy Markdown

PR Summary

Medium Risk
Major-version upgrade of concurrent maps used on the HarPC networking path; compile/test CI is the main guard against API breakage.

Overview
Bumps the workspace scc (scalable concurrent containers) dependency from 2.4.0 to 3.0.0 in Cargo.toml, with Cargo.lock refreshed for the resolved graph (notably scc 3.8.3, new transitive saa, upgraded sdd, and assorted lockfile churn such as windows-sys / spin pins).

There are no application source changes in this PR; harpc-net and harpc-server remain the direct consumers (e.g. HashIndex, ebr::Guard, hash_index::Entry for in-flight RPC transaction tracking).

Reviewed by Cursor Bugbot for commit 65ddeaf. Bugbot is set up for automated code reviews on this repo. Configure here.

@vercel

vercel Bot commented Jan 16, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
ds-theme Error Error Jun 24, 2026 6:30pm
hash Ready Ready Preview, Comment Jun 24, 2026 6:30pm
hashdotdesign Ready Ready Preview, Comment Jun 24, 2026 6:30pm
hashdotdesign-tokens Ready Ready Preview, Comment Jun 24, 2026 6:30pm
petrinaut Ready Ready Preview Jun 24, 2026 6:30pm

@codspeed-hq

codspeed-hq Bot commented Jan 16, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 80 untouched benchmarks


Comparing deps/rs/scc-3.x (65ddeaf) with main (3dbbe7b)1

Open in CodSpeed

Footnotes

  1. 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.

@hash-worker

hash-worker Bot commented Jun 21, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 scc resolved to version 3.8.3, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 3.7.3
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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/deps Relates to third-party dependencies (area)

Development

Successfully merging this pull request may close these issues.

2 participants