Each Angular major version gets 12 months of active support, then 12 months of long term support (LTS), when only critical fixes and security patches are released. After that it is unsupported. Plan to be on a supported major before its LTS window closes.
The policy in plain terms
Angular's release page defines two phases. Active support lasts 12 months, with regularly scheduled updates and patches. LTS lasts another 12 months, and only critical fixes and security patches ship. A fix is considered for an LTS version if it resolves a newly identified security vulnerability, or a regression caused since the start of LTS by a third party change, such as a new browser version.
What the page listed on 19 October 2026
| Version | Status | Released | Active ends | LTS ends |
|---|---|---|---|---|
| 22 | Active | 2026-06-03 | 2027-06 | 2028-06 |
| 21 | LTS | 2025-11-19 | 2026-06-03 | 2027-06 |
| 20 | LTS | 2025-05-28 | 2025-11-19 | 2026-11-28 |
The page also states that Angular versions 2 through 19 are no longer supported. These dates change, so check the release page before you plan, instead of trusting a copy.
What this means for a team
Notice the gap between LTS and active. On LTS you get security fixes but not routine improvements, and some third party libraries stop testing against older majors. A version in its last months of LTS is an upgrade deadline, not a comfort.
Using the table above, an app on version 20 has its LTS window closing on 28 November 2026, which is soon after this review. An app on 19 or lower is already outside the policy.
A simple upgrade rhythm
- Put the LTS end date of each app's Angular version in your tracker as a due date.
- Aim to be on a version in active support, or at worst early LTS.
- Move one major at a time. Angular's deprecation policy keeps deprecated APIs for at least one major version, about a year, which gives you a runway.
- Update the CLI and build tooling together with the framework, since npm dependency updates that require app changes come only in major releases, according to the policy.
- Run a dependency scan after each upgrade, since the new major brings new transitive packages.
Which findings come with an old version
An out of support Angular version means framework flaws found later may never be fixed for you. It does not change app-level mistakes such as bypassSecurityTrust calls, which you control. Fix those anyway.
Try it yourself
Click through it at your own pace, or open it full screen. Look at how ongoing monitoring surfaces new findings on a project you thought was done.
Safeguard's dependency scanning covers front-end projects, and the free scan at gold.safeguard.sh/scan takes a few minutes.
Quick check
Does LTS include new features?
No. Per the policy, LTS releases only critical fixes and security patches.
Can I skip several majors at once?
The deprecation policy is built around one major at a time. Skipping works for some teams but removes the runway the policy gives you.
Sources
Last reviewed: 19 October 2026.
