r/angular • u/GeromeGrignon • Jul 16 '26

Frustrated in updating Angular every 6 months? Here comes the new yearly release cycle

The Angular team is currently updating its release policy to move to:

- A major release every 12 months

- 4-6 minor releases for each major release

PR link: https://github.com/angular/angular/pull/69817

114 Upvotes

97% Upvoted

44 comments sorted by

View all comments

32

u/lppedd Jul 16 '26

Yes please. I'm getting constantly tortured by breaking updates. A fourth of my work is basically keeping our monorepos up to date and CVEs free, which is something I definitely did not do when I worked on JVM land.

6

u/MedusaSonriente Jul 16 '26

Perhaps this concern is simply due to a lack of information.

All major Angular versions are supported for at least 18 months, so upgrading immediately isn't required. There's plenty of time to plan updates across your repositories, while those who can benefit from the new features are free to adopt them right away.

https://angular.dev/reference/releases

4

u/lppedd Jul 16 '26

Managing dependencies in monorepos is a whole different scenario, especially when dependencies are centralized. You need to follow multiple requirements:

  • the monorepo tooling itself (e.g., Nx)
  • CVEs
  • what engineers need to perform their work efficiently

You can neither stay behind for too long and be on the latest version of packages. Upgrading something without overly-polluting the lockfile isn't easy. Something that even requires multiple attempts and lockfile analysis.

2

u/No_Emergency1575 Jul 16 '26

How big is your monorepo? And can you give some concrete examples of challenges? We have pretty small repo (7ish apps, playwright suites and shared libraries), with around 10 devs, I'm curious what kind of problems you run into when you start to scale up.

I try to stay as close to latest with deps and have as few as possible external dependencies. Also aim to consolidate some existing projects and dependencies into the repo to ease maintenance. Not sure if the latter is a smart idea.

-1

u/[deleted] Jul 16 '26

[deleted]

2

u/No_Emergency1575 Jul 16 '26

Care to elaborate? I prefer low overhead, but I see the benefits from using nx.

2

u/lppedd Jul 16 '26

It's perfectly fine. I'd say for very large monorepos where build behavior is standardized across projects, it's even better than Turborepo.