npm installs v0.6.1 instead of v0.7.0

[mudetz]

Describe the bug
Hey there!
First of all: Thank you for this amazing tool! It has saved me from introducing buggy code many times.

Regarding the bug: It's probably my fault but I have tried everything and I really need some fresh eyes on this.
The issue: I cannot install this package on version 0.7.0 using npm
When I install I get 0.6.1 instead

To Reproduce
Steps to reproduce the behavior:
Start with a clean environment (i.e. a clean linux installation with npm freshly installed)

1. Command that was run
   Run npm install elm-open-api@0.7.0 and then npx run elm-open-api --help
2. Expected output
   Something that displays version 0.7.0 and generates code with features of that version
3. Actual output

elm-pages run Cli <entryFilePath> [--output-dir <output-dir>] [--module-name <module-name>] [--effect-types <effect-types>] [--generateTodos <generateTodos>] [--auto-convert-swagger] [--swagger-conversion-url <swagger-conversion-url>] [--swagger-conversion-command <swagger-conversion-command>] [--swagger-conversion-command-args <swagger-conversion-command-args>]... [--server <server>] [--overrides <overrides>]... [--write-merged-to <write-merged-to>] # 
version: 0.6.1

options:
  [... truncated the rest of the output...]

4. Link, or snippet of relevant Open API Spec, if possible
   None relevant, but using npm install elm-open-api 0.7.0 does not give me the features of 0.7.0 and only 0.6.1 instead

Additional context
I took a look at the files installed in the node_modules directory and it seems it installs all the source files for v0.7.0 but the compiled executables under dist/ are built for v0.6.1
Could you please confirm whether the published executables are compiled for the correct version? If this is not the issue I'll have to visit a psychiatrist haha

[wolfadex]

Hi @mudetz, happy to hear this tool is helping. I'm fairly confident that there's a bug with 0.7.0 with the name of the version in some places being outdated, but the code itself being accurate.

There are 2 people working on a large refactor of the tool over the past number of months. There isn't a timeline but with this upcoming release the version numbers should accurately align.

Hope that helps.