Skip to content

Cargo update before v8.1.0 #8346

@michaelsproul

Description

@michaelsproul

Description

We should do a cargo update, or at least a cargo update -p tokio to silence the warning about the bug in tokio (https://github.com/sigp/lighthouse/security/dependabot/68). We're not actually vulnerable to this bug (we do not misuse tokio in a way that would trigger the issue), but it would still be nice to update.

Additional Info

We could chill on this issue until a few other refactor PRs which touch the Cargo.lock are merged:

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency filev8.1.0Post-Fulu release

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions