SonarQube plugin is part of the official Cursor marketplace, but it is still referencing version 2.1 of the plugin, from May 2026. From this thread we understood that “Every update in Cursor Marketplace goes through a manual review before it’s published:”, but it is not clear whether we should trigger this update process somehow ourselves or not.
Based on my understanding and observations, updating the plugin version in the plugin.json and marketplace.json configuration files maintained in the plugin source should be sufficient to roll out a new version. Cursor checks for newer plugin versions when it restarts, and installed users should receive the update if a newer version is available.
We have observed this behavior with plugins distributed through GitHub without being published in the official Cursor Marketplace. I would expect the same update mechanism to apply to Marketplace-listed plugins as well, although this has not been officially confirmed.
One possibility is that fresh installations through the official Marketplace may still receive the older version if the Marketplace listing has not yet been refreshed. However, once the updated version is available to Cursor’s plugin update mechanism, users should receive the newer version on a subsequent Cursor restart.
Therefore, I believe updating the plugin source and version configuration should be the first step. We can still confirm with the Cursor team whether Marketplace updates require an additional submission or review, or whether publishing a new GitHub release or tag is necessary.
You don’t need to resubmit the publish form, and a GitHub release or tag isn’t required! Official Marketplace plugins are pinned to a specific commit and don’t update on their own when you push. Each update is reviewed and then re-synced from your repo on our side, which is why the listing is still on 2.1.
I’ve gone ahead and resynced the repo, but feel free to reach out to [email protected] in the future!