You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No 3 is because the Addon author doesn't always (really they should) update the version number even though there has been a new commit so that's not a core issue the AddonManager is doing it's best with the info provided.
No 3 is because the Addon author doesn't always (really they should) update the version number even though there has been a new commit so that's not a core issue the AddonManager is doing it's best with the info provided.
Well, these requirements must be listed in the Addon developer's technical manual, to enforce uniformity in all addons' behavior.
Here is a simple example of this non-uniformity:
The screenshots below show that the addon developers do NOT follow a uniform standard for extended tooltips:
We need a concise checklist for the addon developers when they submit a new/modified version.
(I have no clue how to include such a checklist in the GitHub workflow. I am not a coder.)
Further, why are some entries blank?
Don't the addon developers tag the latest version at all?
Also, surely the Ribbon WB never had a 0.0.0 version.
(I am actively involved in testing of Ribbon WB, and I know the versions are 1.7.x or 1.8.x.)
So how did AM pick up that odd number??
luzpaz
changed the title
The Addon Manager reports wrong version numbers, or does not report any version number at all
AddonManager: reports wrong version numbers or does not report any version number at all (1.1.0dev r40504)
Mar 12, 2025
Is there an existing issue for this?
Problem description
Here is a screenshot of AM after I updated 4 WBs.

There are four different problems:
(Then why did it update?)
Full version info
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: