Ember 4.0 Tracking Issue

Summary

The purpose of this issue is to provide a way to track the status of the work necessary to ship v.4.0 of Ember.js

The list of issues should be updated to include links to individual issues as they are created. The individual issues should contain more details for each item on this list.

As a reminder: Major versions of Ember do not ship new features- instead, major versions remove previously deprecated features. To read more about Ember’s philosophy regarding editions, please see https://emberjs.com/editions/.

Issues

• blocking Remove deprecated features (See #19617 for open tasks) (includes IE11 removals)
• Tracking for Remove jQuery by Default - Done from the Ember 4.0 perspective.
• 🔒 Ember.assign deprecation implementation https://github.com/emberjs/ember.js/pull/19649
• blocking Deprecation guide for Ember.assign
• 🔒 Ember auto location deprecation implementation https://github.com/emberjs/ember.js/pull/19510 - we got this in targeting 4.1
• non-blocking for 4.0 🔒 Deprecation guide for auto https://github.com/ember-learn/deprecation-app/pull/882
• non-blocking: Remove classic examples from API docs
• blocking Make sure we aren’t showing deprecated methods in the guides - mostly done except willTransition/didTransition
• blocking Update the optional features guide - has a PR
• blocking Update the Octane upgrade guide - has a PR
• Land https://github.com/emberjs/ember.js/pull/19825 otherwise newly generated files will error due to the newer version of eslint-plugin-qunit in the 4.0 new project blueprint
• New browser-support policy: One to drop IE11 from Ember Data CI.
• blocking New browser-support policy: Need a canonical place to publish supported browsers, and we need to have the list for 4.0 in hand. And write it into the blog post.
• blocking The implicit injection of the store, which is deprecated, was not deprecated in all cases. @igorT has seen an OSS codebase that broke on 4.0 upgrade because the case was missed. This should be addressed as a release bugfix improving the fidelity of the deprecation. https://github.com/emberjs/data/pull/7744

Communication

Some of this may happen after release, and is implicitly non-blocking.

• Ember.js website updates. Audit the situation and approve by checking this box.
• Add 4.x section to the deprecation guide https://github.com/ember-learn/deprecation-app/issues/898
• Make sure API docs work. They should after release, confirm by checking this box.
• Make sure the Super Rentals app is happy. Check this box the day after we release the final beta of 4.0 and have a green build. https://github.com/ember-learn/super-rentals-tutorial/actions/runs/1451232432
• Ember 4.0 release blog post tracking issue and Pull request

[simonihmig]

Here’s a PR for dropping IE11: https://github.com/emberjs/ember.js/pull/19558 🎉

[mansona]

I found another thing that could possibly go in the Bugs/Blockers section: https://github.com/emberjs/ember-render-modifiers/pull/33

Essentially we recommend the use of ember-render-modifiers in the guides here but that PR is blocking it from being used in Ember Beta (4.0). I don’t have permission to edit the tracking issue so could someone else add it for me?