Hello, I want to add a new subversion of the plugin.
My question is: for version 2025.1.1, should the release version be 20251 or 202511, assuming 2025.1 exists?
<product-descriptor … release-version=“20251”/> vs
<product-descriptor … release-version=“202511”/>
Documentation says that:
release-date (required)
Date of the major version release in the YYYYMMDD format.
release-version (required)
A major version in a special number format.
The major version is 2025.1, which is why I’m asking. If I push 202511 now, will there be any conflict with 20252 later? Because number 202511 > 20252
It seems that the key point is that this number must increase. I’ll set it to 2025101, and for the next major version, I’ll use 2025200, 2025201, 2025202, and so on. This way, the number will always grow. Does that work for you? @karol.lewandowski
[edit] 2025101 did not pass verification, 202511 pass but then 202520 will not works.
So it seem that versions like 2025.1, then 2025.1.1 and again 2025.2 is not supported by marketplace
It (the release-version) identifies what is considered to be a major release, and it is tied to the release-date.
You should not modify the release date if you did not change the release-version.
Please tell me if I’m wrong, I think the logic is:
We need to manage perpetual license fallback. When you get a perpetual license after 12 months, you can use a specific version for life. Let’s say 2025.1. 2025 is the Year and 1 the Major version. A perpetual license gives you access to all the minor releases, per example 2025.1.1, 2025.1.2.
This is why, when publishing a minor release, you should keep the same release-version and the same release-date. The license management does not look at the “version” (at least, the result is the same), but it looks at the release-version and release-date to identify what is attached to your perpetual license.
And yes, when publishing a new Year or Major version, you have to increase the release-version. At least, I don’t see any reason to decrease this number.
If you want to offer a patch for an old release, do a Minor release, which does not require a new release-version and release-date. Nota: I did not try .
One last thing: the release-version has to follow some rules. This is new, and paid plugins that have been created before this rule can use any release-version number, like 1 or 2. We still have to increase this number when publishing a new Year / Major release.
I wanted to mention that because this can be confusing, especially if you have several old and newer paid plugins.
Thanks @jonathanlermitage.1 Ok, I understand the idea of the release version number as you mentioned. But how do I create a subversion? If I send a new version of the plugin with a new date and subversion (e.g., 2025.1.1), I get an error (as shown in the screenshot). So I cannot upload 2025.1.1 with release-version=“20251”
Ok. I re-read your post. So the problem is only with date yes? That is counterintuitive. So I should leave the same date even if I publish plugin much later
Yes, because a new date or a new release-version would mean this is a major release.
I agree, this is not super intuitive
The marketplace team helped me a lot with that. This is how I published versions 2025.1.1, .2 and .3 of one of my plugins. If you look at their plugin.xml, I use the same release-version and release-date.
I’m sorry to be a bit late to this discussion! Jonathan explained it correctly: you should keep the release-version and release-date the same for your updates, only increasing the version number. I agree it’s not very intuitive, but I hope it’s clear now, and you won’t encounter any issues with future releases.
The only point I’d like to add is that setting a new release-version/date also resets trials . As a result, increasing the release version with every update essentially allows some sneaky users to continuously access your plugin through trial periods.
Thank you, Natalia. This is really important information (about trials) I wasn’t aware of. I noticed that JetBrains tests AI agents in support. This is something that I missed when I worked with them on the initial plugin upload. It ended with an endless Q&A loop. You’re already a step ahead - you anticipate potential questions & issues.
.