workshopsoft/ludic
2
0
Fork 0
Code Issues Pull requests Projects Releases 26 Packages Wiki Activity Actions

chore(release): v0.5.1
All checks were successful
bootstrap / cfree-fixpoint (push) Successful in 23s
Details
ci / build-and-test (push) Successful in 2m54s
Details
commit-lint / conventional-commits (push) Successful in 1s
Details
docs / build-and-deploy (push) Successful in 33s
Details
release / publish (push) Successful in 2m43s
Details

Browse source
This commit is contained in:
Orkun ÇAKILKAYA 2026-09-05 22:22:40 +03:00
parent 44e752b606
commit a916fa5118
3 changed files with 17 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

16
CHANGELOG.md
View file

@ -7,6 +7,22 @@ change type. Preview the next one with `ludic dev release --dry-run`.
A released section may carry a hand-written summary paragraph above its groups
(v0.2.0 has one); the generated bullets below it are not edited by hand.
## v0.5.1 — 2026-09-05
### Fixes
- `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.
`install.sh` also now puts `ludic` on `PATH` for every shell, not just the one
`$SHELL` names. The PATH edit lives in one file (`~/.ludic/env`) that each
profile sources, and the profiles are chosen to cover what people actually open:
`~/.profile` for sh and login bash, `~/.zshenv` because zsh never reads
`~/.profile`, `~/.bashrc`/`~/.bash_profile` when they already exist, and fish's
config when fish is installed. Re-running the installer does not add a second
copy, and `--no-modify-path` still touches nothing.
## v0.5.0 — 2026-09-05
### Features

2
VERSION
View file

@ -1 +1 @@
0.5.0
0.5.1

14
changes/version-from-install-root.md
View file

@ -1,14 +0,0 @@
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.
`install.sh` also now puts `ludic` on `PATH` for every shell, not just the one
`$SHELL` names. The PATH edit lives in one file (`~/.ludic/env`) that each
profile sources, and the profiles are chosen to cover what people actually open:
`~/.profile` for sh and login bash, `~/.zshenv` because zsh never reads
`~/.profile`, `~/.bashrc`/`~/.bash_profile` when they already exist, and fish's
config when fish is installed. Re-running the installer does not add a second
copy, and `--no-modify-path` still touches nothing.