restructure the release blog and start adding ember-cli sections

mansona · mansona · commit d3cd79c3d6e6 · 2025-10-24T17:54:21.000+01:00
diff --git a/content/ember-released-6-8.md b/content/ember-released-6-8.md
@@ -12,37 +12,25 @@ tags:
   - version-6-x
 ---
 
-Today the Ember project is releasing version 6.8 of Ember.js and Ember CLI. This release of Ember.js is an LTS (Long Term Support) candidate. LTS candidates prioritize stability over the addition of new features, and have an extended support schedule.
+// TODO add some overally summary here of all the awesome stuff in this blogpost
 
-A release of Ember is comprised of many projects: ember-source, ember-cli, and all the learning team projects. We follow a [6-week release train](http://emberjs.com/releases/) that includes alpha and beta cycles to ensure changes are well-tested. We encourage our community (especially addon authors) to help test the beta builds and report any bugs before they are published as a final release. The `ember-try` addon is a great way to continuously test your projects against the latest Ember releases. While we only consider the release to be complete upon publication of the blog post, the 6-week cycle is anchored by the release of the ember-source package at the beginning of the process. Releases x.4, x.8 and x.12 will become an LTS candidate, so checkout [Ember LTS Releases](https://blog.emberjs.com/announcing-embers-first-lts/) if you want to know more.
-
----
+Today the Ember project is releasing version 6.8 of Ember.js and Ember CLI. This release of Ember.js is an LTS (Long Term Support) **candidate**. LTS candidates prioritize stability over the addition of new features, and have an extended support schedule.
 
-## Ember.js
+## Ember.js v6.8 
 
-Ember.js is the core framework for building ambitious web applications.
+Ember.js 6.8 introduces 3 key features, 2 new things for Ember developers to use today and a new way to publish the `ember-source` package. 
 
-### Changes in Ember.js 6.8
+### Key Features
 
-Ember.js 6.8 is an incremental, backwards compatible release of Ember with bug fixes, performance improvements, and minor deprecations.
+#### Trusted publishing
 
 v6.8.0 of `ember-source` is the first minor version of the package to be published to `npm` with [Trusted Publishing](https://docs.npmjs.com/trusted-publishers). We will be implementing this across all our packages.
 
 At the bottom of the [npm package page](https://www.npmjs.com/package/ember-source), you'll find a section labeled 'Provenance' that provides verification that the package contents were published from the source repository.
 
-#### Bug fixes
-
-Ember.js 6.8 introduces 1 bug fix.
-
-- Removes unnecessary package ember-cli-htmlbars-inline-precompile from component-test blueprint
+#### `renderComponent`
 
-#### Features
-
-Ember.js 6.8 introduces 2 new features.
-
-##### `renderComponent`
-
-The new `renderComponent` API provides a powerful way to render components into any DOM element, making it easier to integrate components in other environments like d3, ag-grid, WYSIWYG editors, and more! This feature is particularly useful for micro applications, REPLs, and "islands"-based tools.
+The new `renderComponent` API provides a way to render components directly into any DOM element, making it easier to integrate components in other environments like `d3`, `ag-grid`, WYSIWYG editors, etc. This feature is particularly useful for micro applications, REPLs, and "islands"-based tools.
 
 `renderComponent` can be imported from `@ember/renderer` and accepts a component definition along with configuration options:
 
@@ -66,68 +54,121 @@ The API supports several configuration options including:
 - `args`: Arguments to pass to the component - these can be a `trackedObject`
 - `owner`: Optional owner object for service access, (or minimal partial implementation of what your component needs)
 
-[Live Demo](https://limber.glimdown.com/edit?c=JYWwDg9gTgLgBAbzlApgOwCYqgYQuCNdeAXzgDMp84ByAARRACNsB6VTbbGgbgChQkWIjgwoAQwDGAaxQYA8kwBWKSaQpUQtBszaopMYADcUrSRAA2F1YcIBnXnz7m0d%2BG-EwUcALyiJMnKKKmoAFEh8cHDmAK5oMABccAAMADRwkXDAaJKhAJQiHl4AdLHxANTlcGR8JHn8zvbwAGIQEL5wADxe4BaeKAB8mZ3kwCgWGHYoMAOd1gDm6BgDrRCdrAtLQ1FRCAhFKKUQcTAkJJlRnUwxMDCEcISSFsAyPnsHxdmSZyttlevXW6EbZdVijcaTaZDdY9MB9LwDBrkOJqYD3DhYKD5RCZazwcaMYgdDAQSQxEDEUr6LwAUWsFPioRoGGMNHqmQx2DwBCIjNW6SQ2TuSQJDNI7KiqBgMSgaDgouI-HOfG6jDh-RBAGUYP04OJMMgUAZjMAYABPPWoOB2AAW4lQGASTku4ImUxmcxQi0wAwASm0YOtNj6Loh9jqSmVTucdl1AXc5Y9nq93hHDl8fqt-qx48DhmCxm6oZlMntQpyoHkzirWLD4YMgA&format=gjs&shadowdom=on)
-
 You can read more about this on the page for [RFC #1068](https://rfcs.emberjs.com/id/1099-rendercomponent/)
 
-##### `@ember/reactive/collections`
+#### `@ember/reactive/collections`
 
 Ember 6.8 introduces a new package `@ember/reactive/collections` that provides built-in tracking utilities for common collections. This package includes tracked versions of JavaScript's native collection types: `trackedArray`, `trackedObject`, `trackedMap`, `trackedSet`, `trackedWeakMap`, and `trackedWeakSet`.
 
 These utilities offer performance and ergonomics improvements over what has been used via public APIs.
 
 ```gjs
 import { trackedArray } from '@ember/reactive/collections';
+import { on } from '@ember/modifier';
 
-const items = ['apple', 'banana'];
-const addItem = (arr, item) => arr.push(item);
+const items = trackedArray(['apple', 'banana']);
+
+// usually you would have the pushed item be dynamic but this is just a demo
+const addItem = (item) => items.push('cherry');
 
 <template>
-  {{#let (trackedArray items) as |list|}}
-    {{#each list as |item|}}
-      <div>{{item}}</div>
-    {{/each}}
-
-    <button {{on 'click' (fn addItem list 'cherry')}}>
-      Add Item
-    </button>
-  {{/let}}
+  {{#each items as |item|}}
+    <div>{{item}}</div>
+  {{/each}}
+
+  <button type="button" {{on "click" addItem}}>
+    Add Item
+  </button>
 </template>
 ```
 
-[Live Demo](https://limber.glimdown.com/edit?c=JYWwDg9gTgLgBAbzjKBDAxgawKYBMCCUaAnnAL5wBmUEIcA5AALYgBG2UA9FNhjMADdsndBAA2Y7On4QAdgGd6AbgBQoSLERw55KjTpMW7LiAi5glYB2Vrw0eEkqzd1Wg2ZsOnABbYxYa1UVUQV4YBgWeTgAXjgAbXpUMDBJegAaBlZUWWzUegBdVRD5eFRcXABJCLpYgApUIgzwlgBKGIA%2BOAaoADowAFd5b1rmkBaggB5qlNQI9pU4RAQAYkl4WpQMHAIiVFJR%2BTbUKIAfMWASk7IyBcWl5d50bzhzkq7T0aubu7uJ8wF2ggEKNrhNOP95j8gZxHt5rrdFgi4BNWP0YDAdECdPR0OcsPQ4LUnF1ylUWC8LvAcb4iMR6C1rpCfnB8OU4GSQEiwaj0XImdC1vCwdMxLNsO0gA&format=gjs)
-
 You can read more about this on the page for [RFC #1068](https://rfcs.emberjs.com/id/1068-tracked-collections/)
 
 This feature was inspired by `tracked-built-ins` and brings these essential reactivity primitives directly into the framework core.
 
-#### Deprecations
+### Bug fixes
 
-Ember.js 6.8 introduces 0 new deprecations.
+Ember.js 6.8 introduces 1 bug fix.
 
-For more details on changes in Ember.js 6.8, please review the [Ember.js 6.8.0 release page](https://github.com/emberjs/ember.js/releases/tag/v6.8.0-ember-source).
+- [#20988](https://github.com/emberjs/ember.js/pull/20988) Removes unnecessary package ember-cli-htmlbars-inline-precompile from component-test blueprint
+
+#### Deprecations
+
+Ember.js 6.8 introduces no new deprecations.
 
 ---
 
-## EmberData
+## Ember CLI v6.8
 
-EmberData is the official data persistence library for Ember.js applications.
+Ember CLI v6.8 introduces Ember CLI 6.8 introduces 5 new features.
 
-EmberData 5.7 has been released, and along with EmberData 5.6, 5.5 and 5.4, there are many updates that will be more extensively covered in a full stand alone blog post.
+### Key Features
 
-EmberData is also in the process of rebranding to WarpDrive. Stay tuned for more info!
 
-To learn about the motivation and goals for upcoming changes to EmberData in 5.x,
-read the [blog post, EmberData 5.X Update](https://blog.emberjs.com/ember-data-5-x-update-2023-04-15/).
+#### Embroider and Vite by default
 
-<!-- alex ignore retext-equality -->
+This is the first release that enables Embroider by default 🎉 This has been a monumental effort by the whole community over many years and it represents a new era for Ember developers. The improvements to the developer experience and new capabilities are so numerous that they deserve their own blog post but here are some of the highlights
 
-This will help you form the mental model of what to expect across the 5.x series,
-and understand deprecation removals in the context of the upcoming goals.
+- Lightning-fast rebuild speeds thanks to using [Vite](https://vite.dev/) in development
+- Smaller and faster production builds because we no longer use AMD in production
+- You can now use any rollup-plugin or vite plugin to augment your build - no more need for ember-cli specific addons
+- More explicit build tooling - e.g. your Babel config is part of your app and no-longer managed by ember-cli, hidden away from you
 
----
+These are just some of the highlights, but one key theme that has been true throughout the effort to make Vite the default build system for Ember apps is that we now have an oportunity to integrate much more seemlessly with the wider JS ecosystem. Ember is no longer working in a walled garden, forced to re-implement every good idea that the JS community comes up with. If someone comes up with a Vite plugin that does something cool, chances are that adding it to your Vite config in your Ember app will just work!
+
+
+
+// new blueprint - enabled by default for ember new
+
+// ember-cli-update won't update you - use ember-vite-codemod
+
+// generate a classic app - please don't - but if you need to
+
+// look at the RFC for more details about the new bluerpint
+
+ 
+* [#10802](https://github.com/ember-cli/ember-cli/pull/10802) enable Vite blueprint by default for `ember new`
 
-## Ember CLI
+#### Component and Route `--strict` by default
+
+
+
+* [#10831](https://github.com/ember-cli/ember-cli/pull/10831) enable `--strict` by default in classic blueprints to match new Vite app blueprint
+
+### Other Features
+
+- [#10844](https://github.com/ember-cli/ember-cli/pull/10844) throw an error when `ember (generate|destroy) (http-proxy|http-mock|server)` is used in a Vite-based project
+- [#10804](https://github.com/ember-cli/ember-cli/pull/10804) Support a `--ts` alias for the `addon`, `init` and `new` commands
+- [#10791](https://github.com/ember-cli/ember-cli/pull/10791) update the format of the ember-cli-update.json to directly target the blueprint used to generate
+
+### Bug fixes
+
+Ember CLI 6.8 introduced 5 bug fixes.
+
+- [#10826](https://github.com/ember-cli/ember-cli/pull/10826) move resolution of @ember/app-blueprint to prevent loading latest and always load the direct dependency of ember-cli
+- [#10782](https://github.com/ember-cli/ember-cli/pull/10782) update heimdall-fs-monitor to fix error in Node 24
+- [#10803](https://github.com/ember-cli/ember-cli/pull/10803) Add "ember-blueprint" to keywords in `package.json` for the classic blueprints `@ember-tooling/classic-build-addon-blueprint` and `@ember-tooling/classic-build-app-blueprint`
+- [#10798](https://github.com/ember-cli/ember-cli/pull/10798) Add `@warp-drive/ember/install` to remove deprecation when generateing a classic app import from ember-data breakage/deprecation
+- [#10707](https://github.com/ember-cli/ember-cli/pull/10707) Enabled recommended configs from eslint-plugin-n and eslint-plugin-qunit in the classic app blueprint
+
+### Deprecations
+
+Ember CLI 6.8 introduces 2 new deprecations.
+
+#### `ember init` with file names or globs
+
+`ember init` is a little known (and under documented) functionality of the `ember-cli` blueprint system. An even less known functionality was the ability to filter the files that get reinitilised by a path or a glob when running `ember init`. We know that this was a mostly unknown feature because it was never added to the `ember init --help` documentation and it has been broken for some time. Instead of trying to fix it for all the new blueprints we opted to deprecate the functionality. You can read more about the deprecation on the [deprecation guide for `init-no-file-names`](https://deprecations.emberjs.com/id/init-no-file-names/)
+
+#### `ember new --embroider`
+
+Generating an ember app with `ember new --embroider` generated an app using Embroider@v3 with Webpack. Since Embroider@v4 and Vite is now the default for newly generated apps and provides a significantly better developer experience, nobody should be generating new apps with Embroider@v3 any more. To support people who haven't yet upgraded from Embroider@v3 to Embroider@v4 yet, we have opted not to make this argument generate a new Vite app and instead deprecated it. You can read more about the deprecation on the [deprecation guide for `dont-use-embroider-option`](https://deprecations.emberjs.com/id/dont-use-embroider-option/)
+
+
+## The Ember Release process
+
+For more details on changes in Ember.js 6.8, please review the [Ember.js 6.8.0 release page](https://github.com/emberjs/ember.js/releases/tag/v6.8.0-ember-source).
+
+Ember.js is the core framework for building ambitious web applications.
 
 Ember CLI is the command line interface for managing and packaging Ember.js applications.
 
@@ -143,19 +184,9 @@ This utility will help you to update your app or addon to the latest Ember CLI v
 
 It is not required to keep Ember CLI versions in sync with Ember and EmberData. After updating ember-cli, you can keep your current version(s) of Ember or EmberData by editing `package.json` to revert the changes to the lines containing `ember-source` and `ember-data`.
 
-### Changes in Ember CLI 6.8
-
-#### Bug fixes
-
-Ember CLI 6.8 introduced <insert number here> bug fixes.
-
-#### Features
-
-Ember CLI 6.8 introduces <insert number here> new features.
-
-#### Deprecations
+A release of Ember is comprised of many projects: ember-source, ember-cli, and all the learning team projects. We follow a [6-week release train](http://emberjs.com/releases/) that includes alpha and beta cycles to ensure changes are well-tested. We encourage our community (especially addon authors) to help test the beta builds and report any bugs before they are published as a final release. The `ember-try` addon is a great way to continuously test your projects against the latest Ember releases. While we only consider the release to be complete upon publication of the blog post, the 6-week cycle is anchored by the release of the ember-source package at the beginning of the process. Releases x.4, x.8 and x.12 will become an LTS candidate, so checkout [Ember LTS Releases](https://blog.emberjs.com/announcing-embers-first-lts/) if you want to know more.
 
-Ember CLI 6.8 introduces <insert number here> new deprecations.
+Ember.js 6.8 is an incremental, backwards compatible release of Ember with bug fixes, performance improvements, and minor deprecations.
 
 For more details on the changes in Ember CLI 6.8 and detailed upgrade
 instructions, please review the [Ember CLI 6.8.0 release page](https://github.com/ember-cli/ember-cli/releases/tag/v6.8.0-ember-cli).
