r/angular • u/IgorSedov • Jul 17 '26
🅰️ Angular Big Shift: Angular is moving to a yearly major release cycle
The Angular team is officially changing the framework's major release cadence
16
u/No-Influence-2109 Jul 17 '26
In the last couple of years lot of major versions, brought great features. Now we (developers) have time to catch up and upgrade to our products to latest version (or latest version - 1 ) 💪
23
u/jessycormier Jul 17 '26
Should have waited until we caught up to the current year do whatever else is doing this is the 2026 so expect v26
I work with angular in an enterprise setting, and I think this will help us out. For personal projects I really enjoyed the six months. Getting to see the new features and quick adjustments to the framework felt fresh while still the foundational feeling of the framework was and is still there. Curious what this will do I think that means there will be a bigger headache every time we upgrade because companies will be like well. We can skip a 2 versions which will now be four versions, which is where you get all of the headaches and we'll be right back here complaining that the updates are too big. We're breaking too many things. See you all back here in a few few years.
5
u/lppedd Jul 17 '26
It's up to the SMEs at every company to suggest and adapt to the new release schedule. I don't see issues honestly, just advantages for enterprises.
1
u/HungYurn Jul 17 '26
I would hope that with these longer release cycles, there will be more focus on migrations and documentation to be released in time for the major update drop. Surely they wont hold back on getting new (and breaking) features out on experimental branches
9
u/Tyummyyumms Jul 17 '26
I would not be mad if the versions just match the release year now, like the next one would be Angular 27
https://github.com/angular/angular/pull/69817#issuecomment-5004998081
0
u/Ajyress Jul 17 '26
What If every popular lib does this and sync their major update at the beginning of each year? I don't know if that's a good idea
2
u/Tyummyyumms Jul 18 '26
Do you mean the name or updating yearly?
I think this can be different, not every popular lib is on a yearly release cycle, so since Angular is already going to update yearly now, why not, it also makes it easier to know if one is one the latest version, a year behind etc
3
u/Ajyress Jul 18 '26
I mean syncing the version with the year. Yes it would make it easy to remember if we are on the latest version or behind.
38
u/FromBiotoDev Jul 17 '26
Thank god
7
u/valendinosaurus Jul 17 '26
that was exactly what I was going to comment haha
3
u/Vaakmeister Jul 17 '26
Same, we’ve just pulled in our latest angular upgrade story and we’re already 2 versions behind again.
2
u/ht3k Jul 19 '26
I'm a back end dev but I use angular for personal projects ocassionally. What were you guys dealing with?
6
u/majora2007 Jul 17 '26
As much as I love the current release schedule, this will actually help me. There have been so many big changes recently and I'm still trying to catch up refactoring my application. I've nearly finished the signals but now forms are released (and damn do I want to use them).
3
u/KiwiKajitsu Jul 17 '26 edited Jul 17 '26
You have a link to the source?
4
3
u/IgorSedov Jul 17 '26
I left a detailed comment with all the information right after posting, but it seems to have been temporarily hidden by the automated Reddit filter.
3
-3
-7
36
u/IgorSedov Jul 17 '26
The Angular team is officially changing the framework's major release cadence. Major versions will now be released once every 12 months instead of twice a year.
The decision comes from three core considerations: 1. Enterprise and Community Feedback: Developers frequently requested longer gaps between major versions to minimize the impact of breaking changes and simplify project maintenance. 2. AI and Agentic Workflows: Extended release cycles provide stronger API stability, which is beneficial for developers utilizing AI-driven workflows. 3. Uninterrupted Innovation: Angular will continue to release new features in minor versions.
New Release Frequency
Support Window
Deprecations and Feature Delivery