OpenDevicePartnership / OpenDevicePartnership/embedded-services

workflows: Come up with rolling `cargo update` strategy

Open
#447 0 comments 0 reactions 1 assignee View on GitHub

@kurtjd is already working on this.

Since Aug 3, 2025.

Dominant language
Rust
Stars
23
Forks
53
Avg merge
2d 20h
Merged PRs (30d)
13

Description

Ideally it would be nice to have the nightly rolling workflow run cargo update and if the build doesn't break, post a PR. However, this can lead to a lot of new dependencies that need auditing. Instead find a strategy that selectively only updates some dependencies that we actually need the latest and greatest of (mainly git deps to other ODP repos and Embassy) to not overwhelm crate auditors.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.