![]() In general, you can expect the following release cycle: We work toward a regular schedule of releases, so that you can plan and coordinate your updates with the continuing evolution of Angular. ![]() After successfully updating to 6.x.x, you can then update to 7.x.x. For example, if you want to update from version 5.x.x to version 7.x.x, we recommend that you update to the latest 6.x.x release first. Follow the instructions to incrementally update to the next major version, testing and validating at each step. If you are updating from one major version to another, it is recommended that you don't skip major versions. For example, if you want to update from 7.0.0 to 7.2.11, then you can update directly you do not need to update from 7.0.0 to 7.1.0 before updating to 7.2.11. If you are updating within the same major version, then you can skip any intermediate versions and update directly to the targeted version. No developer assistance is expected during update. Patch releases are low risk, bug fix releases.We update peer dependencies in minor versions by expanding the supported versions, but we do not require projects to update these dependencies. 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. Minor releases contain new smaller features.When updating to a new major release, you may need to run update scripts, refactor code, run additional tests, and learn new APIs. Major releases contain significant new features, some but minimal developer assistance is expected during the update.The version number is incremented based on the level of change included in the release. ![]() For example, version 7.2.11 indicates major version 7, minor version 2, and patch level 11. This use of semantic versioning helps you understand the potential impact of updating to a new version.Īngular version numbers have three parts:. AngularJS is the name for all v1.x versions of Angular.Īngular version numbers indicate the level of changes that are introduced by the release. If you are currently using AngularJS, see Upgrading from AngularJS. The practices described in this tutorial apply to Angular 2.0 and later. They 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. They strive to ensure that future changes are always introduced in a predictable way. This tutorial contains the practices that they follow to provide you with a leading-edge app development platform, balanced with stability. They 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. Stability is essential for the ecosystem around Angular to thrive.Īngular also share with you the desire for it to keep evolving. Stability ensures that reusable components and libraries, tutorials, tools, and learned practices don't become obsolete unexpectedly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |