As the author of the Custom Module Manager, I try to observe the webtrees custom module versions and updates.
Currently, Custom Module Manager identifies "2.0.1" as the latest available release for the "telegram" module. After checking the background, I found the following root cause: The release "0.2.1" is tagged with a "v2.0.1" tag:
Seemingly "v2.0.1" is a typo and should be "v0.2.1". Custom Module Manager retrieves these release tags from GitHub. Since receiving the "v2.0.1" tag, Custom Module Manager assumes that an update of "telegram" (current version 0.2.1) is available.
Would it be possible for you to change the release tag to "v0.2.1"?
As the author of the Custom Module Manager, I try to observe the webtrees custom module versions and updates.
Currently, Custom Module Manager identifies "2.0.1" as the latest available release for the "telegram" module. After checking the background, I found the following root cause: The release "0.2.1" is tagged with a "v2.0.1" tag:
Seemingly "v2.0.1" is a typo and should be "v0.2.1". Custom Module Manager retrieves these release tags from GitHub. Since receiving the "v2.0.1" tag, Custom Module Manager assumes that an update of "telegram" (current version 0.2.1) is available.
Would it be possible for you to change the release tag to "v0.2.1"?