-
-
Notifications
You must be signed in to change notification settings - Fork 158
Intellij 2025.1 Support #3689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'd be happy for Usually there isn't much that happens between releases that would cause BC issues, and I also hate when plugins do this, so let's just do it. There is also #3681 |
Ah I looked in the issues but didn't think of PRs. I can test your branch if I figure how to build it :) |
I'll publish a release soon with the relaxed buildNumber. |
Here is a build, this is pretty much what we're going to release with. |
So far so good. (cmd/ctrl + click doesn't go to module but it never has for me with this plugin so it must be normal) |
@joshuataylor in case you were waiting for IntelliJ 2025.1 to be officially released, it was 2 days ago. Thanks! |
Awesome, will release.
Not sure what the holiday schedule is like for JB, but given its Easter,
using the GitHub release once it's published would be the only way for now.
…On Fri, 18 Apr 2025, 3:47 pm Francesco Cervone, ***@***.***> wrote:
@joshuataylor <https://github.com/joshuataylor> in case you were waiting
for IntelliJ 2025.1 to be officially released, it was 2 days ago.
https://blog.jetbrains.com/idea/2025/04/intellij-idea-2025-1/
Thanks!
—
Reply to this email directly, view it on GitHub
<#3689 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABW62ZZIDOJR4SFKOCB7WL22CUXVAVCNFSM6AAAAAB2L2VEVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJUHA2DMOJSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
*francescocervone* left a comment (KronicDeth/intellij-elixir#3689)
<#3689 (comment)>
@joshuataylor <https://github.com/joshuataylor> in case you were waiting
for IntelliJ 2025.1 to be officially released, it was 2 days ago.
https://blog.jetbrains.com/idea/2025/04/intellij-idea-2025-1/
Thanks!
—
Reply to this email directly, view it on GitHub
<#3689 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABW62ZZIDOJR4SFKOCB7WL22CUXVAVCNFSM6AAAAAB2L2VEVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJUHA2DMOJSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Uh oh!
There was an error while loading. Please reload this page.
Intellij 2025.1 is currently in beta and this plugin current version is incompatible / allowed up to 243.*
FWIW this plugin is always the last and sometimes only one to not load on new versions. I noticed many other plugins just set "untilBuild" empty or to value like "299.*" to prevent that.
Would that be sensible for intellij-elixir?
The text was updated successfully, but these errors were encountered: