Release tags

[faxik]

Hi, as I see, there are no release tags and it is difficult to roll back to a specific release without diving into commit logs.

With the recent update to esp-idf that introduced problems with mesh (non-)working (espressif/esp-idf#2916, espressif/esp-idf#2915), I wanted to do roll-back but I couldn't figure out which version should I check out.

[OttoWinter]

Same here, tagging releases would be really helpful also for release notifications. Right now, I don't see a way to follow the updates of this library without watching the whole repo.

For me this is important as a package author, AsyncTCP's updates have broken builds quite a few times in the past when using pinned arduino-esp32 versions - esphome/issues#476 ; I understand it's hard to test what will be incompatible with what release, but I'd at least like to get notifications when a new release is out.

[me-no-dev]

generally this lib is rarely updated. After the update now, I do not expect any that will add/change functionality. And to confess, lib versions here are more or less rushed because of some issue.

[fah]

I'm confused:
esphome can reference to versions. But here are no version tags defined.

Dependency Graph
|-- <AsyncTCP> 1.0.3
|-- <ESPmDNS> 1.0
|   |-- <WiFi> 1.0
|-- <FS> 1.0
|-- <ESP Async WebServer> 1.2.2
|   |-- <AsyncTCP> 1.0.3
|   |-- <WiFi> 1.0
|   |-- <FS> 1.0
|   |-- <ArduinoJson-esphomelib> 5.13.3
|-- <AsyncMqttClient> 0.8.2
|   |-- <AsyncTCP> 1.0.3

So then this commit (90715ae) is version 1.1.0 or 1.0.4 ?
Is that something that happens inside the platformio registry?

[stale]

[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[stale]

[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions.