I can’t publish a new version of my plugin because my release version is invalid. I knew this for ages and the reason I haven’t fixed it is because it would require my customers having a fallback license to purchase a new version again.
Is there a way to prevent that?
What are your previous and new release-date and release-version? And the error message?
The release date was 20210205 something but the version was just “6”. It was at the beginning of the marketplace so it was fine but now I can’t update it without having customers to build a new license.
What if you publish a plugin with the same 20210205 release-date and “6” release-version? You may only update the version tag, per example, by adding an extra “.1” or “-1”. If you do that, is there any error message?
Invalid plugin descriptor ‘plugin.xml’. The parameter [61] and the plugin version [9.8.0] should have a matching beginning. For example, release version ‘20201’ should match plugin version 2020.1.1
I’ve tried many options, “61”, “980”, “9801”, nothing works.
Is there a way to prevent this verification to happen?
I published it from the website for now. Can’t waste more time on this.
Hi,
Sorry for the inconvenience! This check should not apply to plugins that initially had different release versions and versions. That’s why you were able to upload it on the website without any issues.
We are also fixing this in the Gradle plugin to ensure it won’t block future updates.