johnhenley
commented
7 months ago I think you are seeing these "phantom" versions due to DNN telemetry picking up "news" of a version that really doesn't exist or hasn't yet been released.
In this case 9.13.3 has just been released and you got an early notification:)
DNN has a "phone home" mechanism that sends versions for the platform and installed modules back to dnnplatform.io with the intention of collecting and corellating version information across the platform's ecosystem and sharing that information with the vendors and community. What sometimes happens though, is that a module developer might have DNN installed and be working on a module's repository (or fork of a module repository) and bumps the version in their internal build/version. But since they don't know about or perhaps forget to turn off this feature, their "update" makes its way into the telemetry, and gets pushed out to the ecosystem as a potential new version.
How do I know this? Because I've caused false updates to appear as available because I test the community forums builds on a dev version of my production site, and I forget to remove the option. :)
So yes it is frustrating. When you see a new module listed, visit the vendor or, if it's a community-built module, https://github.com/DNNCommunity.
Is there an existing issue for this?
What happened?
When I installed 9.13.2, there is a prompt on the persona bar to show that 9.13.3 is available but currently the version hasn't been released yet, we only have the RC release.
Steps to reproduce?
Current Behavior
Expected Behavior
we should only prompt for the final releases.
Relevant log output
No response
Anything else?
No response
Affected Versions
9.13.2 (latest release)
What browsers are you seeing the problem on?
Chrome
Code of Conduct