From 11adf365db132e78950a956eab024bc79547932a Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 7 Sep 2026 12:38:19 +0000 Subject: [PATCH] Describe the NodeJS pinning as the one change it is MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `EmberCli::App#node_engine` had a CHANGELOG entry of its own, next to the entry for the pinning it exists to serve. It is not a separate decision for a reader to make — nothing asks them to call it — so listing it separately implied two changes where there is one. The surrounding sections already draw the line this way: `0.13.1` and `0.13.2` each describe one change in one entry while naming every method it touches, and `0.13.0` splits into entries only where each one asks the reader for a separate decision — enabling the development server, raising the `ember-cli-rails-assets` requirement, configuring `origin`. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_014rAfkAVGVifbaEoTVeT66u --- CHANGELOG.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 43049c96..d002f3af 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,9 +8,8 @@ main * Replace `EmberCli::App#yarn_enabled?` with `EmberCli::App#yarn?` * Pin the NodeJS version in the `package.json` that `rails generate ember:heroku` writes, from the `engines.node` the Ember applications - declare. Applications that declare different versions are left unpinned -* Add `EmberCli::App#node_engine`, reading `engines.node` from the Ember - application's `package.json` + declare, read through the new `EmberCli::App#node_engine`. Applications + that declare different versions are left unpinned 0.13.2 ------