Incompatible: requires IDE build 203 or older
plugin (for those who do not want to collect himself): idea-gitignore-3.2.3.203.zip
Any ETA on this, @hsz? 2020.3 is out currently.
There are still a couple of issues to resolve, but I'm working on that. I hope to release it next week.
@hsz is there any way we can help?
@ruurd Thanks, it's almost done as I just described it here: https://twitter.com/hszanowski/status/1335306406682103808
Tests are green, everything builds well – I just need to verify if everything works as previously since there was a giant refactoring done.
@Mereo4 We are waiting for the release to be released. In the meantime, you can manually install the fix that I applied above - I do not feel any problems with it yet


Yes, I'm sorry, I just deleted my comment as I misread... I thought the new version was already deployed.
As a side question: Is the message given wrongly-phrased?
I am on 203.* version, and it says:
Incompatible: requires IDE build 203 or older
i.e. >= 203,* (let's assume decimals, it makes my argument easier)
So, my 203,* >= requires 203,*... what gives? I would expect it would say e.g.:
Incompatible: requires IDE build 202 or earlier
OK I installed ...203 and that crashes Rubymine for some reason... Fixed it by clobbering its cache but still. Would you be interested in a crashlog? Hmm. Seems a one-off. Weird. I tried reproducing in WebStorm and Intellij and no problems.
All right - I've prepared a release version for the plugin compatible with 2020.3.
Since it contains not only version bumped but also a bunch of refactorings and compatibility fixes to make it aligned to the IJ SDK 203 (as described in Tweet mentioned above), I'd like to ask you for a manual installation of the attached archive and checking if nothing is broken.
Thanks, folks!
Why don't you want to set up an EAP publishing channel in plugins.jetbrains.com, the way JetBrains recommends?
@BorzdeG I've prepared an automated EAP release process that depends on the version name - i.e. v4.0.0-eap will publish artifact to the eap channel instead to the default one.
Such GitHub integration is taken from the IntelliJ Platform Plugin Template.
For now, I didn't go that way simply because I care about the feedback collected here. The latest version published in EAP three years ago channel was downloaded 400+ times only.
It makes sense. It's too bad that getting EAP plugin versions is cumbersome. I'd use more of them in the past if they were easily accessible - like Rider EAP or prerelease NuGet packages.
In fact, I've published 4.0.0-eap to the EAP channel this morning anyway.
@marcinsmialek Since now – having a properly working CI and fixing all the compatibility issues and integration with Plugin Verifier tool – providing the pre-releases will be much easier.
We'll include the EAP channel in the everyday work for that plugin.
@marcinsmialek The EAP version of the plugin has nothing to do with the EAP version of the IDE - they can exist separately
Most helpful comment
There are still a couple of issues to resolve, but I'm working on that. I hope to release it next week.