fix(deps): bump @angular/* from 19.2.20 to 19.2.23 - #7019
Closed
dependabot[bot] wants to merge 2 commits into
Closed
fix(deps): bump @angular/* from 19.2.20 to 19.2.23#7019dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
|
Bumps [@angular/common](https://github.com/angular/angular/tree/HEAD/packages/common) from 19.2.20 to 20.3.25. - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/v20.3.25/packages/common) --- updated-dependencies: - dependency-name: "@angular/common" dependency-version: 20.3.25 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
bobbor
force-pushed
the
dependabot/npm_and_yarn/angular/common-20.3.25
branch
from
July 13, 2026 16:04
ce5b4fa to
043e77a
Compare
The root package.json resolutions pinned all @angular/* framework packages to exact 19.2.20, which prevented the patched @angular/common version from resolving. Bump all 9 framework resolutions to 19.2.23 (they release in lockstep) and revert the ^20.3.25 ranges to ^19.2.23 since Angular 20 is not required to remediate alert 524.
bobbor
changed the title
Member
|
Changed direction on this PR 👋 Dependabot alert 524 only needs @angular/common >= 19.2.23, not Angular 20. The root package.json resolutions pinned all @angular/* to exact 19.2.20, which blocked the patched version from resolving — bumped all 9 framework resolutions to 19.2.23 and reverted the ^20.3.25 ranges to ^19.2.23. The Angular 20 upgrade is parked in #7047. |
Member
|
Closing in favor of the Angular 20 upgrade in #7047, which remediates all 9 open @angular/* Dependabot alerts (verified against the full GHSA advisory ranges: the 20.x lines are patched at 20.3.22/20.3.25, and #7047 pins 20.3.26). The 19.2.23 bump here would only cover 5 of the 9 alerts — the remaining 4 (529, 537, 538, 539) have no patched version in the 19.x line since Angular 19 is EOL. |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/angular/common-20.3.25
branch
July 14, 2026 13:30
bobbor
added a commit
that referenced
this pull request
Jul 15, 2026
Upgrades the Angular library and example app from Angular 19 to 20.3, making the Angular 20 move real and consistent (supersedes the effectively-cosmetic @angular/common-only bump in #7019). Dependencies: - All @angular/* -> 20.3.26 (runtime + compiler-cli); @angular/cli & @angular-devkit/build-angular -> 20.3.x - ng-packagr -> ^20.3; @angular-eslint/* -> ^20.7; @testing-library/angular -> ^18.1; ng-mocks -> ^14.15 - typescript -> ~5.8 (Angular 20 requires >=5.8 <5.9) - Root package.json resolutions bumped (these pinned all @angular/* to 19.2.20 and were the reason the prior bump never took effect) Code: - Migrated constructor DI to field inject() across 19 component/directive files via Angular's official inject() schematic (required by @angular-eslint/prefer-inject, newly enforced in angular-eslint 20) Testing: - Library build: PASS - Unit tests (jest): PASS (15 suites / 43 tests) - Lint (tsc + eslint): PASS - The example-app @environments/*/aws-exports build failure is pre-existing/environmental (missing e2e-generated config), not caused by this upgrade
bobbor
added a commit
that referenced
this pull request
Jul 16, 2026
Upgrades the Angular library and example app from Angular 19 to 20.3, making the Angular 20 move real and consistent (supersedes the effectively-cosmetic @angular/common-only bump in #7019). Dependencies: - All @angular/* -> 20.3.26 (runtime + compiler-cli); @angular/cli & @angular-devkit/build-angular -> 20.3.x - ng-packagr -> ^20.3; @angular-eslint/* -> ^20.7; @testing-library/angular -> ^18.1; ng-mocks -> ^14.15 - typescript -> ~5.8 (Angular 20 requires >=5.8 <5.9) - Root package.json resolutions bumped (these pinned all @angular/* to 19.2.20 and were the reason the prior bump never took effect) Code: - Migrated constructor DI to field inject() across 19 component/directive files via Angular's official inject() schematic (required by @angular-eslint/prefer-inject, newly enforced in angular-eslint 20) Testing: - Library build: PASS - Unit tests (jest): PASS (15 suites / 43 tests) - Lint (tsc + eslint): PASS - The example-app @environments/*/aws-exports build failure is pre-existing/environmental (missing e2e-generated config), not caused by this upgrade
bobbor
added a commit
that referenced
this pull request
Jul 16, 2026
Upgrades the Angular library and example app from Angular 19 to 20.3, making the Angular 20 move real and consistent (supersedes the effectively-cosmetic @angular/common-only bump in #7019). Dependencies: - All @angular/* -> 20.3.26 (runtime + compiler-cli); @angular/cli & @angular-devkit/build-angular -> 20.3.x - ng-packagr -> ^20.3; @angular-eslint/* -> ^20.7; @testing-library/angular -> ^18.1; ng-mocks -> ^14.15 - typescript -> ~5.8 (Angular 20 requires >=5.8 <5.9) - Root package.json resolutions bumped (these pinned all @angular/* to 19.2.20 and were the reason the prior bump never took effect) Code: - Migrated constructor DI to field inject() across 19 component/directive files via Angular's official inject() schematic (required by @angular-eslint/prefer-inject, newly enforced in angular-eslint 20) Testing: - Library build: PASS - Unit tests (jest): PASS (15 suites / 43 tests) - Lint (tsc + eslint): PASS - The example-app @environments/*/aws-exports build failure is pre-existing/environmental (missing e2e-generated config), not caused by this upgrade
bobbor
added a commit
that referenced
this pull request
Jul 16, 2026
Upgrades the Angular library and example app from Angular 19 to 20.3, making the Angular 20 move real and consistent (supersedes the effectively-cosmetic @angular/common-only bump in #7019). Dependencies: - All @angular/* -> 20.3.26 (runtime + compiler-cli); @angular/cli & @angular-devkit/build-angular -> 20.3.x - ng-packagr -> ^20.3; @angular-eslint/* -> ^20.7; @testing-library/angular -> ^18.1; ng-mocks -> ^14.15 - typescript -> ~5.8 (Angular 20 requires >=5.8 <5.9) - Root package.json resolutions bumped (these pinned all @angular/* to 19.2.20 and were the reason the prior bump never took effect) Code: - Migrated constructor DI to field inject() across 19 component/directive files via Angular's official inject() schematic (required by @angular-eslint/prefer-inject, newly enforced in angular-eslint 20) Testing: - Library build: PASS - Unit tests (jest): PASS (15 suites / 43 tests) - Lint (tsc + eslint): PASS - The example-app @environments/*/aws-exports build failure is pre-existing/environmental (missing e2e-generated config), not caused by this upgrade
bobbor
added a commit
that referenced
this pull request
Jul 16, 2026
* chore(angular): upgrade @aws-amplify/ui-angular to Angular 20 Upgrades the Angular library and example app from Angular 19 to 20.3, making the Angular 20 move real and consistent (supersedes the effectively-cosmetic @angular/common-only bump in #7019). Dependencies: - All @angular/* -> 20.3.26 (runtime + compiler-cli); @angular/cli & @angular-devkit/build-angular -> 20.3.x - ng-packagr -> ^20.3; @angular-eslint/* -> ^20.7; @testing-library/angular -> ^18.1; ng-mocks -> ^14.15 - typescript -> ~5.8 (Angular 20 requires >=5.8 <5.9) - Root package.json resolutions bumped (these pinned all @angular/* to 19.2.20 and were the reason the prior bump never took effect) Code: - Migrated constructor DI to field inject() across 19 component/directive files via Angular's official inject() schematic (required by @angular-eslint/prefer-inject, newly enforced in angular-eslint 20) Testing: - Library build: PASS - Unit tests (jest): PASS (15 suites / 43 tests) - Lint (tsc + eslint): PASS - The example-app @environments/*/aws-exports build failure is pre-existing/environmental (missing e2e-generated config), not caused by this upgrade * chore(angular): require Angular >= 20 in ui-angular peerDependencies Adds a major changeset for @aws-amplify/ui-angular since Angular 19 and below are no longer supported. * chore: allow LGPL rollup-plugin-dts (ng-packagr build tooling) in dependency review Adds a license allowlist exception for rollup-plugin-dts (LGPL-3.0-only, transitive build-time dep of ng-packagr@20) and extends the README License Note accordingly. * refactor(examples): migrate remaining angular example components to inject() Completes the inject() migration for consistency across the library and example app, addressing review feedback. The library files were migrated via the official Angular inject() schematic, which was run against the library workspace only, so these example components were missed. * refactor(examples): migrate remaining useAuthenticator examples to inject() Completes constructor-DI removal across the angular example app.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @angular/common from 19.2.20 to 20.3.25.
Release notes
Sourced from @angular/common's releases.
... (truncated)
Changelog
Sourced from @angular/common's changelog.
... (truncated)
Commits
06be298fix(http): preserve empty referrer option in HttpRequest9f443bcfix(common): Limits date format string lengthfa940e1fix(http): Rejects non-HTTP(S) URLs in JSONP requests1a62130fix(common): use cryptographically secure SHA-256 for transfer cache key gene...566ad05fix(common): skip transfer cache for uncacheable HTTP traffice2ef1cefix(http): skip transfer cache for fetch credentialed requests3d135cefix(common): add upper bounds for digitsInfo39a4b4cfix(common): sanitize placeholderde7b2a6fix(http): exclude withCredentials requests from transfer cache4233188fix(http): skip TransferCache for cookie-bearing requests by defaultDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.