Can we make it more obvious which version of esp-generate targets which version of esp-hal (and friends)

[bjoernQ]

Maybe this is a non-issue but

• the latest released version of esp-generate targets the latest released version of esp-hal ... that is nice and easy

But how could a user know what older releases are targetting?

Obviously looking at the template's Cargo.toml for a specific release tag is the answer right now but that's a bit cumbersome.

• should we at least add a way to show the version we are targetting
• should we align the versioning?

As said - it was never a big deal to me and I don't know if it's a big deal for users - just wondering if there is something we should/want to do about it

[SergioGasquez]

should we align the versioning?

This would be dificult imho, as sometimes we need patch releases only on one of them, like with esp-hal@1.0.0 we did esp-generate@1.0.0 and esp-generate@1.0.1

should we at least add a way to show the version we are targetting

We could print it somewhere, maybe a log when using cli mode and maybe include it on the title of the TUI?

[bjoernQ]

Ah true ...

We could print it somewhere, maybe a log when using cli mode and maybe include it on the title of the TUI?

That's probably a good thing to have, yes! And I just realized we usually have it in the release notes for a GH release - maybe we should be a bit more consistent with that

[MabezDev]

I think printing all the esp-* crates versions in the templates toml could be good, but I wouldn't go much further than that here I think.