Extension version mismatch for ElixirLS

[jjcarstens]

The VSCode extension lists version 0.9.0, but it downloads ElixirLS v0.8.2 (which doesn't actually exist). I assume this is related to elixir-lsp/elixir-ls#644 and elixir-lsp/elixir-ls#637

Probably not a huge except that you'll have confusing details when trying to debug issues and see the bad version in the output

[brainlid]

I came to report the issue as well. Trying to get HEEx template formatting working. I can see Elixir-LS shows release 0.9.0... but the changelog shows it as "Unreleased".

I'm just not sure if I have the correct version installed or if I need to update anything.

Running the formatter reports this error in the output:

Started ElixirLS v0.8.2
Elixir version: "1.13.4 (compiled with Erlang/OTP 24)"
Erlang version: "24"
ElixirLS compiled with Elixir 1.10.4 and erlang 22
MIX_ENV: test
MIX_TARGET: 
[Info  - 5:20:55 PM] Compile took 1489 milliseconds
[Info  - 5:20:55 PM] [ElixirLS Dialyzer] Checking for stale beam files
[Info  - 5:20:56 PM] [ElixirLS WorkspaceSymbols] Indexing...
[Info  - 5:20:56 PM] [ElixirLS Dialyzer] Found 0 changed files in 77 milliseconds
[Info  - 5:20:56 PM] [ElixirLS Dialyzer] Analyzing 0 modules: []
[Info  - 5:20:56 PM] [ElixirLS WorkspaceSymbols] Module discovery complete
[Info  - 5:20:56 PM] [ElixirLS Dialyzer] Analysis finished in 63 milliseconds
[Info  - 5:20:56 PM] [ElixirLS WorkspaceSymbols] 27 callbacks added to index
[Info  - 5:20:56 PM] [ElixirLS WorkspaceSymbols] 203 modules added to index
[Info  - 5:20:57 PM] [ElixirLS WorkspaceSymbols] 350 types added to index
[Info  - 5:20:57 PM] Dialyzer analysis is up to date
[Info  - 5:20:57 PM] [ElixirLS Dialyzer] Writing manifest...
[Info  - 5:20:58 PM] [ElixirLS Dialyzer] Done writing manifest in 1879 milliseconds.
[Error - 5:21:03 PM] Request textDocument/formatting failed.
  Message: Unable to format due to syntax error
  Code: -32603 

That last error message is what is displayed when I try to run the formatter. I can't tell what the problem is. Currently thinking it's the version mismatch?

[holandes22]

I though the same, but not sure is related to the version mismatch now as using the version from main branch yields the same error.
More details here #242

[lukaszsamson]

Closing as it's fixed in 0.10.0