From 22378d79c3c452e0a7533e42cd22b566fa0a4b05 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 11 Sep 2026 17:32:58 +0000 Subject: [PATCH 1/2] Say which blueprint each unreleased entry changes Every entry since 0.14.0 touches one blueprint and not the other, and two of them read as though they touched both: the build failure reporting is the classic blueprint's `ember build --watch` path only, and moving to `vite build` leaves `ember build` in place for classic applications. Say so, and put the entries in the order someone upgrading would want them: what changes how their application is built, then what was broken, then what was only untidy. Co-Authored-By: Claude Opus 5 --- CHANGELOG.md | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a910c21c..91ff3e5e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,25 +1,29 @@ main ------ -* Pass `--watcher` to `ember build` only when the build watches. The flag - names the backend that watches the file system, so it did nothing for a - one-off build * Build a Vite-based application with `vite build`, the command its own `build` script runs, rather than with `ember build`. `ember build --help` calls itself a "Vestigial command in Vite-based projects" and points at - that script. The output is unchanged; `silent` now quiets such a build - with `--logLevel error` rather than `ember build --silent` + that script. What the build writes is unchanged, and so is the classic + blueprint, which keeps building with `ember build`. The `silent` option + now quiets a Vite build with `--logLevel error`, which drops the progress + output and keeps the errors * Recognise an application as Vite-based from any of the six names Vite resolves its configuration from, rather than only `vite.config.js`, `vite.config.mjs` and `vite.config.ts`. An application configured in `vite.config.mts`, `vite.config.cts` or `vite.config.cjs` was taken for a classic one and served with `ember build --watch`, which a Vite-based project rejects -* Report the whole `ember build` failure in the `EmberCli::BuildError` - message, instead of only its first line. The line naming the file that - failed to build is rarely the first one the build tool writes, so a parse - error was reported with its message and line number but no way to tell - which file it came from +* Report the whole build failure of a classic application in the + `EmberCli::BuildError` message, instead of only its first line. Such an + application builds in the background, and `BuildMonitor` turns what + `ember build --watch` writes into the exception; the line naming the file + that failed to build is rarely the first one, so a parse error arrived + with its message and line number but no way to tell which file it came + from +* Pass `--watcher` to `ember build` only when the build watches. The flag + names the backend that watches the file system, so it did nothing for a + one-off build 0.14.0 ------ From 3224fc7099e3c70c2916e546dac3fa61c620f2d6 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 11 Sep 2026 17:33:08 +0000 Subject: [PATCH 2/2] Release 0.14.1 A Vite-based application is built with vite build, the command its own build script runs, and is recognised from any of the six names Vite resolves its configuration from. A classic application's build failure is reported whole rather than one line of it, and ember build is no longer given --watcher for a build that does not watch. Co-Authored-By: Claude Opus 5 --- CHANGELOG.md | 2 +- lib/ember_cli/version.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 91ff3e5e..7bdeca59 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,4 +1,4 @@ -main +0.14.1 ------ * Build a Vite-based application with `vite build`, the command its own diff --git a/lib/ember_cli/version.rb b/lib/ember_cli/version.rb index 58fac09c..67212672 100644 --- a/lib/ember_cli/version.rb +++ b/lib/ember_cli/version.rb @@ -1,3 +1,3 @@ module EmberCli - VERSION = "0.14.0".freeze + VERSION = "0.14.1".freeze end