Closed screamerbg closed 6 years ago
ARM Internal Ref: IOTCLT-2290
Mbed tool chain doesn't support versions, all the hashes are only hashes. Therefore, the versions are more or less irrelevant. Closing out, won't be fixed.
@JanneKiiskila, the mbed toolchain DOES support versions. This applies for mbed OS and all example programs, including mbed CLI - see log above. If you're referring to mbed Client lacking versioning after some point then that exactly what I'm asking to be fixed.
Hmm... I wonder why I've not ever seen a single mbed-OS release update mbed-os.lib
change come in with a version number, they are always with hashes? Why is that then?
mbed releases
doesn't seem to work at least on Windows, fails for me at least. I raised an issue on that.
https://github.com/ARMmbed/mbed-cli/issues/594
So, it is new tool feature for mbed-cli, everyone should update their mbed-cli's then...
Why is the tool listing all versions for the components? The list is too long.. I would understand if you used something like --all to get ALL the versions, but for now - it should just list ONE version (the one that's used) OR the hash (if no version match).
Raised an issue on that; https://github.com/ARMmbed/mbed-cli/issues/596
Won't fix.
While using mbed CLI 1.3.0 (latest at the time of this writing), I've noticed that newer version of this example program uses non-official version of mbed Client and other libraries.
For example mbed-os-example-client in mbed-os-5.6.1 tag/release uses mbed Client version 3.0.0
mbed-os-example-client in the latest/mbed-os-5.7.0 release uses unknown version of mbed Client
Also looking at the releases available for all libraries, the latest mbed-os-example-client doesn't use release version of the following libraries:
Full log is available below.
Can someone add release tags to these libraries/repositories? CC @JanneKiiskila @yogpan01 @MarceloSalazar