Sitelet https://github.com/angular/angular-cli/compare/v20.3.27...v20.3.28
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: angular/angular-cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v20.3.27
Choose a base ref
...
head repository: angular/angular-cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v20.3.28
Choose a head ref
  • 5 commits
  • 11 files changed
  • 2 contributors

Commits on Jun 11, 2026

  1. fix(@angular/cli): fallback to deprecated versions when resolving ran…

    …ges if no non-deprecated version is found
    
    When using ng update to resolve package version ranges on the command line in 20.3.x, we previously skipped deprecated package versions entirely during pre-validation. In cases where all versions satisfying the range are deprecated, this resulted in update failure. Now, we attempt to find a satisfying version from non-deprecated versions first, and fallback to deprecated versions if none are found. This aligns the CLI pre-validation with the update schematic resolution logic.
    
    Additionally, in the update schematic, we align package group versions to the resolved version of the group leader instead of using the unresolved range, and we remove the check that prevented aligning already-present packages. This ensures that when a package in the group (like @angular/animations) is deprecated, it is correctly aligned with the other group members, preventing peer dependency conflicts during update.
    alan-agius4 committed Jun 11, 2026
    Configuration menu
    Copy the full SHA
    e3d5646 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    241f9b9 View commit details
    Browse the repository at this point in the history
  3. fix(@angular/cli): remove forceAuth and unscoped credential parsing

    Remove the non-standard forceAuth option and custom parsing for unscoped registry
    credentials (token, username, password, auth) in package-metadata.ts.
    
    Since the npm CLI does not support unscoped credentials and ignores them by
    default, this aligning removes the unnecessary parsing complexity. Unscoped
    credentials will now behave identically to any other standard configuration
    property, falling through to default configuration parsing.
    clydin committed Jun 11, 2026
    Configuration menu
    Copy the full SHA
    f12e170 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    2fb9b3b View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    9eba41c View commit details
    Browse the repository at this point in the history
Loading