Skip to content

Update Angular dependencies to use ^ for semver #21925

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
dgp1130 opened this issue Oct 11, 2021 · 1 comment · Fixed by #22571
Closed
2 tasks done

Update Angular dependencies to use ^ for semver #21925

dgp1130 opened this issue Oct 11, 2021 · 1 comment · Fixed by #22571
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

Comments

@dgp1130
Copy link
Collaborator

dgp1130 commented Oct 11, 2021

🚀 Feature request

Command (mark with an x)

  • new
  • update

Description

Angular applications are generated via ng new to include a package.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.

@dgp1130 dgp1130 added feature Issue that requests a new feature freq1: low Only reported by a handful of users who observe it rarely workaround1: obvious area: @schematics/angular labels Oct 11, 2021
@ngbot ngbot bot modified the milestone: Backlog Oct 11, 2021
dgp1130 pushed a commit that referenced this issue Jan 27, 2022
…version prefix

With this change we update Angular dependencies to use `^` instead of `~` as version prefix.

Closes #21925
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant