-
Notifications
You must be signed in to change notification settings - Fork 2k
chore(deps): update angular-cli monorepo to v20 (major) #3144
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
Open
+2
−2
Conversation
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
@renovate
renovate
bot
added
the
dependencies
Pull requests that update a dependency file
label
Nov 19, 2024
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: nestjs-docs@1.0.0
npm error Found: @angular/compiler-cli@18.2.8
npm error node_modules/@angular/compiler-cli
npm error dev @angular/compiler-cli@"18.2.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler-cli@"^20.0.0" from @angular-devkit/build-angular@20.2.2
npm error node_modules/@angular-devkit/build-angular
npm error dev @angular-devkit/build-angular@"20.2.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-09-03T21_31_25_884Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-03T21_31_25_884Z-debug-0.log
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
7 times, most recently
from
November 25, 2024 22:30
2356d21
to
728d081
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
7 times, most recently
from
December 11, 2024 08:26
7ba8445
to
9efeff5
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
4 times, most recently
from
December 18, 2024 08:28
d385b94
to
d9e208e
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
2 times, most recently
from
December 20, 2024 08:57
f5c792d
to
c96dd8b
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
2 times, most recently
from
January 15, 2025 11:17
43f8eb8
to
60596ef
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
6 times, most recently
from
January 17, 2025 14:03
fffd596
to
536a7b2
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
2 times, most recently
from
June 11, 2025 17:08
39ab921
to
3101794
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
2 times, most recently
from
June 18, 2025 11:47
26a0f0d
to
e8c5848
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
5 times, most recently
from
July 2, 2025 08:09
62bdb45
to
71aead3
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
3 times, most recently
from
July 9, 2025 22:53
14209f5
to
415a8df
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
4 times, most recently
from
July 23, 2025 21:35
26c37ab
to
07fc052
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
3 times, most recently
from
July 30, 2025 23:15
6b78061
to
c6e6197
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
2 times, most recently
from
August 6, 2025 21:42
2424228
to
fa8cf75
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
from
August 13, 2025 15:37
fa8cf75
to
eeff4ae
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
3 times, most recently
from
August 27, 2025 07:34
6b2638a
to
81401ff
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
3 times, most recently
from
September 2, 2025 08:19
f9fe3cc
to
d4f5153
Compare
@renovate
renovate
bot
force-pushed
the
renovate/major-angular-cli-monorepo
branch
from
September 3, 2025 21:31
d4f5153
to
ad26dab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
18.2.9
->20.2.2
18.2.9
->20.2.2
Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v20.2.2
Compare Source
@angular/cli
@angular/build
v20.2.1
Compare Source
@angular/cli
@schematics/angular
@angular-devkit/schematics-cli
@angular/build
v20.2.0
Compare Source
@angular/cli
@schematics/angular
@angular-devkit/schematics
@angular/build
v20.1.6
Compare Source
@schematics/angular
typeSeparator
in the library schematicv20.1.5
Compare Source
@angular/cli
v20.1.4
Compare Source
@angular/cli
@angular/build
v20.1.3
Compare Source
@angular/build
vite
to7.0.6
v20.1.2
Compare Source
@angular/cli
define
option is being included multiple times in the JSON help@angular-devkit/core
v20.1.1
Compare Source
@angular/build
outputHashing
is set toall
orbundles
when HMR is enabledv20.1.0
Compare Source
@angular/cli
@schematics/angular
@angular-devkit/build-angular
@angular/build
@angular/ssr
loadChildren
runs in correct injection context during route extractionv20.0.6
Compare Source
@schematics/angular
@angular/build
@vitest/browser/context
from esbuild bundlingv20.0.5
Compare Source
@angular-devkit/build-angular
@vitejs/plugin-basic-ssl
dependency@angular/build
/
to/base
v20.0.4
Compare Source
@schematics/angular
@angular/ssr
v20.0.3
Compare Source
@schematics/angular
main.server.ts
intsconfig.files
when presenttypeSeparator
when generating applications@angular/build
v20.0.2
Compare Source
@schematics/angular
less
as a devDependency when selected as the style preprocessor@angular/build
v20.0.1
Compare Source
@angular/cli
@schematics/angular
@angular/build
v20.0.0
Compare Source
Breaking Changes
@angular/cli
Node.js v18 is no longer supported with Angular.
Before updating a project to Angular v20, the Node.js version must be
at least 20.11.1. For the full list of supported Node.js versions,
see https://angular.dev/reference/versions.
Node.js versions from 22.0 to 22.10 are no longer supported
@schematics/angular
--server-routing
option has been removed from several schematics. Server routing will be used when using the application builder.@angular-devkit/schematics
The
NodePackageLinkTask
has been removed without a replacement. Create a custom task if needed.Note: This does not affect application developers.
@angular/build
@schematics/angular
moduleResolution
tobundler
@angular/build
in new projects--server-routing
option@angular/ssr
dependency only whenprovideServerRendering
import has been updated.ng.html
extensionwithAppShell
.ng.html
file extension.component
extension/typeprovideServerRoutesConfig
toprovideServerRendering
scripts
option value from new applicationsoutputPath
option value from generated applications@angular/cli
@angular-devkit/build-angular
@angular-devkit/schematics
NodePackageLinkTask
@angular/build
browser
optioncomposite
option with Angular compilercom.chrome.devtools.json
is consistently served after initial runcom.chrome.devtools.json
if project is moved@angular/pwa
@angular/ssr
provideServerRendering
and removeprovideServerRouting
AngularNodeAppEngine
,AngularAppEngine
, andprovideServerRouting
APIs@angular/router
@ngtools/webpack
v19.2.15
Compare Source
@angular-devkit/build-angular
v19.2.14
Compare Source
@angular/build
| Commit | Type | Desc
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.