Problems with plugin version comparison

IntelliJ Platform
1

I release versions of my plugin for each IntelliJ version that I support, using versions like 2026.2.1-eap1-262 - that means version 2026.2.1-eap1 of my plugin, compiled for the 262 platform. Users are having a lot of problems with that latest version (2026.2.1-eap1-262). If they’re on version 2026.2-262, it does not offer to upgrade to 2026.2.1-eap1-262. If they manually install that version, the IDE then offers the “upgrade” 2026.2.1-eap1-262 → 2026.2-262.

One user has addtionally reported that if they’re on 2026.2-262 it does offer the upgrade to the EAP, but then immediately offers the erroneous downgrade, causing an endless loop.

I’ve never had problems with this before, this looks like a marketplace bug?

2

After some investigation, this does seem to be a version comparator problem, caused by the difference in the number of components to the version. Previously I used x.y.z versions which always had three components, but sometimes using versions like 2026.2 and sometimes 2026.2.1 messes up the comparisons in the presence of other modifiers like eap1.

3

Hi,
I have escalated this to the JetBrains Marketplace team.

4

Meanwhile it might help that the latest update is the latest by the upload date, not by necessary by semantic versioning.