Hi, first of all thank you for all the work that goes into maintaining ElixirLS. It’s a critical tool for a lot of us working daily with Elixir.

I’ve noticed a recurring problem though: after many recent updates to the VSCode extension, something new tends to break whether it’s features that were working previously, new bugs introduced, or compatibility issues. The most difficult part is that these breakages often come without prior notice or clear mention in the changelog/release notes.

This creates a lot of friction:

It makes developers hesitant to update, since updates can unexpectedly disrupt workflow.

It’s difficult to know if an issue is a new regression, a known compatibility change, or something misconfigured locally.

Possible suggestions:

Add clearer release notes highlighting breaking changes or known incompatibilities.

Consider adopting a more explicit versioning strategy (e.g., semver with clear indication when breaking changes are introduced).

Even a short “known issues” section per release would help users prepare.

I completely understand that this is open source work and it takes a lot of effort. My intent here is not to criticize the work being done, but to raise awareness that the update process has been painful lately and see if there’s a way to make it smoother for everyone.

Thanks again for maintaining this project. I think a bit more communication around releases would go a long way.