Orkuncakilkaya
29fcef3b9c
`ludic version` looked for bin/ludicc and VERSION relative to the working directory. In the toolchain repo that is right by accident; from a project — the only place a user runs it — there is no ./bin, so a perfectly good install answered "(version unknown)". It now resolves the compiler through ludic_home(), like every other command. The regression test asked for the version from the repo root, so it passed for the same accidental reason the bug hid behind; it now asks from the staged project, where the answer can only come from the install. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
6 lines
343 B
Markdown
6 lines
343 B
Markdown
bump: patch
|
|
type: fix
|
|
`ludic version` reports the version of the toolchain it belongs to. It looked for
|
|
`bin/ludicc` and `VERSION` beside the *current* directory, so it answered
|
|
"(version unknown)" from a project — which is the only place a user ever runs it.
|
|
It now resolves the compiler through the install root, like every other command.
|