Confluence 5.5.4 was not published to the Marketplace correctly

Customers reported today that the UPM told them they were running an unknown, incompatible version of Confluence. As such, administrators were unable to check add-ons for compatibility or search within the UPM for new add-ons.

Upon inspection I noticed that Confluence 5.5.4 was listed in Marketplace admin, but was not published.

I have now manually corrected this problem.

Keeping the Marketplace site in sync with versions released in HAMS is an important part of the build process. Failing to do this causes confusion and friction for customers and wastes time in raised support tickets.

This is a recurring issue, and is continuing to cause frustration for me as the person who receives these problem reports and has to solve them.

At one point in history this process was part of an automated build. Marketplace has a REST API for version management. How is this still happening?

This is the fourth time in the last year or so that this has happened, requiring manual intervention from a Marketplace administrator to correct, and worse so, goes un-noticed until a customer or an add-on vendor reports this problem.

The way in which this is continuing to happen sporadically is a clear indicator that the current process is broken. I am interested to hear how the Confluence team intends to fix this.