CP: Update badge on up to date site

[marcorieser]

Bug description

Sometimes the changelog for an addon does not get updated which causes an update badge in cp even if everything is up to date. In my case it's the Translation Manager addon. But found an issue that seems like to underline my case: #6718

How to reproduce

No idea but installing the Translation Manager addon probably reproduces the issue atm.

Logs

No response

Environment

Environment
Application Name: Wizard Live
Laravel Version: 11.10.0
PHP Version: 8.3.7
Composer Version: 2.7.6
Environment: local
Debug Mode: ENABLED
URL: statamic-wizard-promotions.test
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Livewire
Livewire: v3.5.0

Statamic
Addons: 5
Sites: 2 (German, English)
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.7.2 PRO

Statamic Addons
jonassiewertsen/statamic-livewire: 3.4.0
marcorieser/statamic-vitals: 1.2.0
marcorieser/tailwind-merge-statamic: 1.1.0
ryanmitchell/statamic-translation-manager: 2.0.0
stillat/relationships: 2.2.0

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[marcorieser]

Just noticed that the version on statamic.com is outdated for the addon (1.6.0 instead of 2.0.0): https://statamic.com/addons/thoughtco/translation-manager

[marcorieser]

According to Rob, releasing a new version of the addon fixes the issue. Probably because that re-pings (or something) the version update and Statamic can pick it up.

[robdekort]

According to Rob, releasing a new version of the addon fixes the issue. Probably because that re-pings (or something) the version update and Statamic can pick it up.

That's true. Perhaps a resave of the addon on statamic.com might also trigger something. Not sure how stuff works, but perhaps it's an issue on statamic.com and not the CMS.

[duncanmcclean]

We've just deployed a fix to Statamic.com which should hopefully prevent this issue from happening in future.

For addons affected by this issue, the addon developer should be able to trigger a re-sync of the product on Statamic.com by resaving their latest release (just edit and re-save, no actual changes are required).

After that, the product's information should be up-to-date within a minute or two.

[robdekort]

Nice. And that’s good to know. I’ll keep an eye out.

[robdekort]

Notice I'm still seeing this in the latest version. You can see Statamic believes Forma isn't up2date.

[marcorieser]

Notice I'm still seeing this in the latest version. You can see Statamic believes Forma isn't up2date.

Has the dev of Forma re-triggered the sync as Duncan mentioned above?

[robdekort]

Has the dev of Forma re-triggered the sync as Duncan mentioned above?

I don't know, I'm not @edalzell. But I think the fix doesn't work:

We've just deployed a fix to Statamic.com which should hopefully prevent this issue from happening in future.

[robdekort]

Ah, the latest release from Forma was before the fix. Gotcha.

@edalzell: would you trigger a save on statamic.com like this: "For addons affected by this issue, the addon developer should be able to trigger a re-sync of the product on Statamic.com by resaving their latest release (just edit and re-save, no actual changes are required)."

[edalzell]

@edalzell: would you trigger a save on statamic.com like this: "For addons affected by this issue, the addon developer should be able to trigger a re-sync of the product on Statamic.com by resaving their latest release (just edit and re-save, no actual changes are required)."

Done.

[robdekort]

Thanks Erin.

Unfortunately this issue doesn’t seem solved then.

Screenshot 1	Screenshot 2