5 lines
14 KiB
JSON
Raw Permalink Normal View History

{
"id": "guide/releases",
"title": "Angular versioning and releases",
"contents": "\n\n\n<div class=\"github-links\">\n <a href=\"https://github.com/angular/angular/edit/master/aio/content/guide/releases.md?message=docs%3A%20describe%20your%20change...\" aria-label=\"Suggest Edits\" title=\"Suggest Edits\"><i class=\"material-icons\" aria-hidden=\"true\" role=\"img\">mode_edit</i></a>\n</div>\n\n\n<div class=\"content\">\n <h1 id=\"angular-versioning-and-releases\">Angular versioning and releases<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/releases#angular-versioning-and-releases\"><i class=\"material-icons\">link</i></a></h1>\n<p>We recognize that you need stability from the Angular framework. Stability ensures that reusable components and libraries, tutorials, tools, and learned practices don't become obsolete unexpectedly. Stability is essential for the ecosystem around Angular to thrive.</p>\n<p>We also share with you the desire for Angular to keep evolving. We strive to ensure that the foundation on top of which you are building is continuously improving and enabling you to stay up-to-date with the rest of the web ecosystem and your user needs.</p>\n<p>This document contains the practices that we follow to provide you with a leading-edge app development platform, balanced with stability. We strive to ensure that future changes are always introduced in a predictable way. We want everyone who depends on Angular to know when and how new features are added, and to be well-prepared when obsolete ones are removed.</p>\n<div class=\"alert is-helpful\">\n<p>The practices described in this document apply to Angular 2.0 and later. If you are currently using AngularJS, see <a href=\"guide/upgrade\" title=\"Upgrading from Angular JS\">Upgrading from AngularJS</a>. <em>AngularJS</em> is the name for all v1.x versions of Angular.</p>\n</div>\n<a id=\"versioning\"></a>\n<h2 id=\"angular-versioning\">Angular versioning<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/releases#angular-versioning\"><i class=\"material-icons\">link</i></a></h2>\n<p>Angular version numbers indicate the level of changes that are introduced by the release. This use of <a href=\"https://semver.org/\" title=\"Semantic Versioning Specification\">semantic versioning</a> helps you understand the potential impact of updating to a new version.</p>\n<p>Angular version numbers have three parts: <code>major.minor.patch</code>. For example, version 7.2.11 indicates major version 7, minor version 2, and patch level 11.</p>\n<p>The version number is incremented based on the level of change included in the release.</p>\n<ul>\n<li><strong>Major releases</strong> contain significant new features, some but minimal developer assistance is expected during the update. When updating to a new major release, you may need to run update scripts, refactor code, run additional tests, and learn new APIs.</li>\n</ul>\n<ul>\n<li><strong>Minor releases</strong> contain new smaller features. Minor releases are fully backward-compatible; no developer assistance is expected during update, but you can optionally modify your apps and libraries to begin using new APIs, features, and capabilities that were added in the release. We update peer dependencies in minor versions by expanding the supported versions, but we do not require projects to update these dependencies.</li>\n</ul>\n<ul>\n<li><strong>Patch releases</strong> are low risk, bug fix releases. No developer assistance is expected during update.</li>\n</ul>\n<div class=\"alert is-helpful\">\n<p><strong>Note:</strong> As of Angular version 7, the major versions of Angular core and the CLI are aligned. This means that in order to use the CLI as you develop an Angular app, the version of <code>@angular/core</code> and the CLI need to be the same.</p>\n</div>\n<a id=\"updating\"></a>\n<h3 id=\"supported-update-paths\">Supported update paths<a title=\"Link to this heading\" class=\"header-link\" aria-hidden=\"true\" href=\"guide/releases#supported-update-paths\"><i class=\"material-icons\">link</i></a></h3>\n<p>In ali
}