Node.js Test CI Security Incident
Ember is a truly community-driven framework, with contributors and core
team members who live all over the world and work for many different
companies. The vast majority of our collaboration happens online via
tools like GitHub.
That said, every quarter the Ember core team likes to meet face-to-face
for a high-bandwidth, high-intensity discussion about the future of the
framework. We focus on high priority issues, ways we can improve our
process, and setting the long-term vision for Ember.
Ember.js 2.3, a minor version release of Ember with backwards compatible
changes, is released today.
Ember.js 2.4 beta, the branch of Ember that will be released as stable in
roughly six weeks, is also being released today.
Changes in Ember.js 2.3
Ember.js 2.3 introduces a number of features we're excited to see in a stable
release.
ember-qunit 0.4.16+ is required for your codebase's test suite to be
compatible with Ember 2.3. See "Introducing Owners and Deprecating Containers"
below for more detail.
Because developers trust Ember.js to handle sensitive customer data in
production, we take the security of the project seriously. The Ember
project maintains a clearly outlined security policy and a
low-traffic mailing list exclusively for security
announcements.