Update Angular dependencies to use ^
for semver
#21925
Labels
area: @schematics/angular
feature
Issue that requests a new feature
freq1: low
Only reported by a handful of users who observe it rarely
workaround1: obvious
Milestone
🚀 Feature request
Command (mark with an
x
)Description
Angular applications are generated via
ng new
to include apackage.json
with~
characters, meaning they only automatically include patch updates to dependencies, not feature updates. This was intended to reduce the risk of breakage due to other dependencies accidentally shipping breaking changes in minor versions (which has happened several times in the past). Downside of this is that Angular deps are not updated as frequently as they could be and we have our own CI systems and integration testing to make sure that we don't introduce breaking changes into a minor versions. There's no need to apply the same requirement to Angular when we're able to more consistently and regularly test each version.Describe the solution you'd like
New applications should be generated with
^
for Angular dependencies and existing applications should be migrated for consistency. If an existing app pins an explicit version (such as"@angular/core": "12.2.4"
), then we should update that as normal but leave the semver string bare so as not to change user's intent.Should be an easy change, though we probably just missed v13. This definitely requires a major version, so the soonest we could do this is v14.
The text was updated successfully, but these errors were encountered: