Closed bhuvanchandra closed 8 months ago
@bhuvanchandra The master branch on GitHub is match with Component Register release version. You can use the master branch on GitHub if you don't add it as an external component.
@lhespress Got it thanks for your suggestion, will do it.
Just a follow-up question, eventually there will be a release or tag in the espnow repo?
@bhuvanchandra You always can use github as a source for component manager:
dependencies:
esp-now:
version: master
path: .
git: https://github.com/espressif/esp-now.git
idf:
version: ">=4.1.0"
Version can point to a branch, tag or commit hash.
@bhuvanchandra Closing this issue since there has been no update on this. Please feel free to reopen if required.
The current versioning across different platforms appears rather perplexing. GitHub shows the latest release as v1.0, the ESP registry lists the most recent version as 2.3.0, and the ESPNow API reports its version as v1.0 when used without adding ESPNow as an external component dependency in the v5.0.2 ESP-IDF. Could anyone guide me as to which is the most relevant version to keep track of?