From b24f0dd572b3e8797072d7b29119309940e0fd52 Mon Sep 17 00:00:00 2001 From: Orkuncakilkaya Date: Sat, 5 Sep 2026 23:15:22 +0300 Subject: [PATCH] chore(release): v0.6.0 --- CHANGELOG.md | 25 +++++++++++++++++++++++++ VERSION | 2 +- changes/docs-deploy-installer.md | 6 ------ changes/split-dev-cli.md | 16 ---------------- 4 files changed, 26 insertions(+), 23 deletions(-) delete mode 100644 changes/docs-deploy-installer.md delete mode 100644 changes/split-dev-cli.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 43f6b618..17525f7f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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 ` becomes `ludic-dev `** 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 diff --git a/VERSION b/VERSION index cb0c939a..a918a2aa 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.5.2 +0.6.0 diff --git a/changes/docs-deploy-installer.md b/changes/docs-deploy-installer.md deleted file mode 100644 index be0a0142..00000000 --- a/changes/docs-deploy-installer.md +++ /dev/null @@ -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`. diff --git a/changes/split-dev-cli.md b/changes/split-dev-cli.md deleted file mode 100644 index ca889407..00000000 --- a/changes/split-dev-cli.md +++ /dev/null @@ -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 ` becomes `ludic-dev `** 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.