Angular Version Evolution
Angular Versioning
The Release Cadence
Angular operates on a predictable schedule, which is great news for developers. A new major version is released every six months. This steady rhythm means you can anticipate when new features will arrive and plan your projects accordingly. It removes the guesswork and helps teams stay current without constant surprises.
Between these major releases, you'll see minor releases and patch releases. Minor releases typically add new, backward-compatible features, while patch releases are focused on fixing bugs. This regular flow of updates keeps the framework secure, efficient, and modern.
Understanding Version Numbers
Angular follows a standard practice called Semantic Versioning, or SemVer. Every version number is broken into three parts: MAJOR.MINOR.PATCH. Each part tells you something specific about the changes in that release.
| Part | Name | What it Means |
|---|---|---|
| 16.2.8 | Major | Contains significant new features. Updating to a new major version might include breaking changes, meaning you may need to update your code. |
| 16.2.8 | Minor | Adds new functionality without breaking existing features. These are safe to adopt. |
| 16.2.8 | Patch | Includes bug fixes. These are also safe to update and are highly recommended to keep your app stable. |
For example, moving from version 16.1.0 to 16.2.0 is a minor update. You get new features, but your existing code shouldn't break. Moving from 16.2.0 to 17.0.0 is a major update. It signals bigger changes, and you'll want to review the update guide before migrating.
Support You Can Count On
The Angular team provides excellent support for its recent versions. Each major release receives 18 months of support, which is divided into two phases.
First, there are 6 months of active support. During this time, the version gets regular minor releases and patches. After that, it enters 12 months of Long-Term Support (LTS).
In the LTS phase, a version only receives critical bug fixes and security patches. This 18-month window gives developers plenty of time to plan and execute their upgrades to the next major version without feeling rushed. It creates a stable, secure environment for building applications.
This predictable cycle of releases and support helps you manage dependencies and keep your applications healthy over the long term.