Open joostecg opened 1 month ago
This is similar to https://github.com/koxudaxi/ruff-pycharm-plugin/issues/383 and it will happen with any new build number. Why don't you just remove until-build
and limit the supported version only after a problem is discovered. I'm using more plugins and they just work when EAP is released.
@koxudaxi I know you are busy with porting to the new LSP integration. Anyway, would you be so kind to just rebuild the current version with updated until-build
so we can use the current version of the plugin in PyCharm EAP. Thank you very much.
Sorry for the slow response. I have tried, but I can't build it properly just by increasing the version. Some APIs cannot be referenced, so something needs to be fixed.
https://github.com/koxudaxi/ruff-pycharm-plugin/actions/runs/9585184135/job/26430490957?pr=461
Describe the bug With each release of and EAP on PyCharm Professional the plugin fails to load or is incompatible with the latest EAP
To Reproduce Steps to reproduce the behavior:
Expected behavior Continued use with latest EAP unless some reason exists that would break the compatibility.
Environments (please complete the following information):