Skip to content

Conversation

@BartMassey
Copy link
Contributor

Updates embassy-nrf to use document-features 0.2.12 (suppresses a warning) and embassy-time-queue to use heapless 0.9 (fixes resolver issues in some builds). Bumps version to 0.9.1.

@BartMassey
Copy link
Contributor Author

Am realizing now that these upgrades are arguable point releases for the other embassy crates, which would touch almost everything here. Advice on making this transition correctly is appreciated.

@lulf
Copy link
Member

lulf commented Jan 6, 2026

I think ideally we'd upgrade heapless across all the crates, not just one of them, to avoid duplicate heapless copies where we can avoid it.

@BartMassey
Copy link
Contributor Author

Agree: might as well upgrade everything that upgrades while we're doing this.

I'm willing to take on the big task of upgrading all the dependencies of all the things if that's cool. TBH I'll probably do it with Claude unless there's some tooling already in place to help with this: it's a lot of error-prone tedium for the most part. Maybe I'll have Claude write the tooling?

I probably should forego upgrading any crates that have breaking changes (except heapless) beyond their point release for now? I don't know how big folks want this to get.

@BartMassey BartMassey changed the title Update dependencies for embassy-nrf and related Update dependencies for embassy-nrf and related (WIP) Jan 6, 2026
@lulf
Copy link
Member

lulf commented Jan 7, 2026

  • Use claude as much as you want, it will be reviewed like any other code
  • Don't bump version numbers, we do this via the release tooling which automatically checks for semver breakages
  • Don't worry about breaking changes. As above, the release tooling will deal with that and in general if heapless is used in a public API for a crate, we'll have to bump the minor version (for pre- 1.0 crates).
  • Thanks for taking on the task :)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants