07:35 <JamesMunns[m]> btw, is a library (like postcard) switching from defmt 0.3 to defmt 1.0 a breaking semver change?

07:36 <JamesMunns[m]> I think it could be maybe confusing if people still have a locked older version of 0.3, but if they update to the latest 0.3 it should be semver compat if postcard uses 1.0?

07:36 <JamesMunns[m]> (context: https://github.com/jamesmunns/postcard/pull/234)

07:39 <burrbull[m]> 0.3.100 is wrapper for 1.x https://crates.io/crates/defmt/0.3.100/dependencies

07:45 <thejpster[m]> <JamesMunns[m]> "btw, is a library (like postcard..." <- The intention was for it not to be, but YMMV

10:39 <davidmpye[m]> Is there any consensus about how to insert credentials eg WiFi details into a binary at compile time, eg via a non standard version of env! ?

10:39 <davidmpye[m]> I have a project that needs to generate a number of different uf2 images, with WiFi credentials baked in, as well as a different 'device name' per binary

10:40 <davidmpye[m]> And just trying to figure out the nearest way to do that

10:40 <diondokter[m]> davidmpye[m]: Could also do an `include_bytes!` or `include_str!`

10:40 <davidmpye[m]> Also in std:: tho?

10:40 <diondokter[m]> Ah different per binary? You could flash a separate bin file to flash

10:41 <diondokter[m]> davidmpye[m]: No that's in core too

10:43 <davidmpye[m]> Oh, env is also in core

10:44 <davidmpye[m]> One nasty way would just to be to knock up a shell script to set the env vars per binary, then cargo build it, and rename the binary, set the env vars, repeat etc.

10:44 <davidmpye[m]> Wonder if there's a neater cargo way to do that

10:44 <diondokter[m]> davidmpye[m]: There's no cargo post build step sadly

13:17 <haobogu[m]> <davidmpye[m]> "Is there any consensus about how..." <- you can do it using build.rs