chore(coprocessor): bytes/time dep upgrade

[Eikix]

What

• Update coprocessor/fhevm-engine/Cargo.lock only.
• Bump vulnerable crates:
  • bytes 1.10.1 -> 1.11.1
  • time 0.3.43 -> 0.3.47

Why

• coprocessor-dependency-analysis/dependencies-check fails on RustSec advisories:
  • RUSTSEC-2026-0007 (bytes)
  • RUSTSEC-2026-0009 (time)

Scope

• Lockfile-only change in coprocessor workspace.
• No runtime code changes.

Local validation

• cd coprocessor/fhevm-engine && cargo update -w --locked
• cd coprocessor/fhevm-engine && cargo-deny deny check license --deny license-not-encountered
• cd coprocessor/fhevm-engine && cargo-audit audit

[rudy-6-4]

I think time was updated already on main, but ok to bump it further.

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for bed7f66.

🟢 All jobs passed!

But CI Insights is watching 👀

[Eikix]

@mergify queue

[mergify]

queue

🛑 The pull request has been closed manually

[mergify]

Merge Queue Status

🛑 Queue command has been cancelled

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: main) at bed7f66

This pull request spent 43 minutes 19 seconds in the queue, with no time running CI.

Reason

Pull request #1938 has been dequeued. The pull request has been closed manually

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.