chore(release): v0.6.0
All checks were successful
bootstrap / cfree-fixpoint (push) Successful in 22s
ci / build-and-test (push) Successful in 2m55s
commit-lint / conventional-commits (push) Successful in 1s
docs / build-and-deploy (push) Successful in 33s
release / publish (push) Successful in 2m44s

This commit is contained in:
Orkun ÇAKILKAYA 2026-09-05 23:15:22 +03:00
parent e175619543
commit b24f0dd572
4 changed files with 26 additions and 23 deletions

View file

@ -7,6 +7,31 @@ 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.6.0 — 2026-09-05
### Refactoring
- **`ludic` is only the language's command line now.** The toolchain's own tasks —
building the compiler from its IR seed, the regression suites, the docs site,
releases — moved out of it into a separate `ludic-dev` binary that is built from
a checkout and is not part of an install.
- **`ludic help` is what a user can actually do**: `new`, `run`, `build`, `test`,
`add`, `fmt`, `lsp`, `doctor`, `upgrade`. No section about a repository they do
not have. Typing `ludic dev …` says where those tasks went rather than failing
as an unknown command.
- **`ludic dev <task>` becomes `ludic-dev <task>`** for contributors; every task
is otherwise unchanged. The bootstrap is now
`bin/ludicc tools/ludic-cli/dev.ludic -o bin/ludic-dev && bin/ludic-dev build`.
- The shipped binary drops from ~880 KB to ~190 KB, since none of the release,
docs-generation or bootstrap machinery is linked into it any more.
### CI
- The docs deploy triggers on a change to `install.sh`. The site publishes the
installer, but the workflow's path filter did not mention it — so a release that
only fixed `install.sh` left the old script live at the URL the landing page
tells people to pipe into `sh`.
## v0.5.2 — 2026-09-05
### Fixes

View file

@ -1 +1 @@
0.5.2
0.6.0

View file

@ -1,6 +0,0 @@
bump: patch
type: ci
The docs deploy triggers on a change to `install.sh`. The site publishes the
installer, but the workflow's path filter did not mention it — so a release that
only fixed `install.sh` left the old script live at the URL the landing page
tells people to pipe into `sh`.

View file

@ -1,16 +0,0 @@
bump: minor
type: refactor
**`ludic` is only the language's command line now.** The toolchain's own tasks —
building the compiler from its IR seed, the regression suites, the docs site,
releases — moved out of it into a separate `ludic-dev` binary that is built from
a checkout and is not part of an install.
- **`ludic help` is what a user can actually do**: `new`, `run`, `build`, `test`,
`add`, `fmt`, `lsp`, `doctor`, `upgrade`. No section about a repository they do
not have. Typing `ludic dev …` says where those tasks went rather than failing
as an unknown command.
- **`ludic dev <task>` becomes `ludic-dev <task>`** for contributors; every task
is otherwise unchanged. The bootstrap is now
`bin/ludicc tools/ludic-cli/dev.ludic -o bin/ludic-dev && bin/ludic-dev build`.
- The shipped binary drops from ~880 KB to ~190 KB, since none of the release,
docs-generation or bootstrap machinery is linked into it any more.