Version 3.3.0

[jessebraham]

Opening as a draft for now, not going to merge/release until Monday.

Just bumped the dependencies, the point of this release is mostly just to get the current changes in main published while we begin work on the next major release. This unfortunately resulted in a pretty hefty bump in the MSRV, but I don't really feel like fighting with different versions to find some middle ground, so it is what it is.

A couple dependencies are still outdated, as we have had issues when trying to update them (addr2line and crossterm). This is something I'd like to address in v4, but again not going to bother with it right now.

[SergioGasquez]

LGTM! Thanks for taking care of this

[kevin-june]

On the subject of MSRV, though a bit of a tangent / some foreshadowing:

Yesterday I encountered this error when installing espflash onto a system that was running Rust 1.82:

Caused by:
  failed to parse manifest at `/Users/jenkins/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bytemuck_derive-1.9.0/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.82.0 (8f40fc59f 2024-08-21)).

After some digging around, it seems that bytemuck_derive had bumped its MSRV to 1.84 (with resolver set to 3) and released this in version 1.9.0. espflash pulls in this requirement through its dependency on bytemuck and its derive feature.

This version was yanked shortly after it was released, so the problem has gone away for now. For context, see the bytemuck_derive's version history and bytemuck/issues/294.

I still find it a bit confusing that the compiler suggested setting edition2024 rather than noting that the MSRV of Rust 1.84 was not met, so I might be missing something....

In any case, this this failure will likely reappear when bytemuck_derive deploys 1.9.0 again. If/when this happens, I hope that this information will help!

[jessebraham]

Thanks for the heads up. I have added a note to the installation instructions to suggest using --locked when installing, which I guess is about as much as we can do about that right now 😅