build: update cross-repo angular dependencies to v21 #4
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
See associated pull request for more information.
|
Closing since we want to use stable version of Angular here. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
angular-robot
deleted the
ng-renovate/cross-repo-angular-dependencies
branch
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.
This PR contains the following updates:
^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-next^20.2.0->^21.0.0-nextRelease Notes
angular/angular (@angular/animations)
v21.0.0-next.4Compare Source
Breaking Changes
common
ngComponentOutletContentis now of typeNode[][] | undefinedinstead ofany[][] | undefined.core
provideZoneChangeDetectionwhile also removing ZoneJS polyfills will no longer result in the
internal scheduler being disabled. All Angular applications now
consistenly use the same scheduler, and those with the Zone change detection
provider include additional automatic scheduling behaviors based on
NgZone stabilization.
for ZoneJS-based change detection by default. Add
provideZoneChangeDetectionto the providers of yourbootstrapApplicationfunction or yourAppModule(if usingbootstrapModule). This provider addition will be covered by anautomated migration.
moduleIdwas removed fromComponentmetadata.interpolationoption on Components has been removed. Only the default{{ ... }}is now supported.common
ngComponentOutletContent(#63674)compiler
aria-invalid(#63748)compiler-cli
core
moduleIdfrom Component metadata (#63482)interpolationoption on Components. (#63474)forms
migrations
v21.0.0-next.3Compare Source
Breaking Changes
compiler-cli
"typeCheckHostBindings": falsein theangularCompilerOptionssection of your tsconfig.core
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
A schematic is provided to automatically update
main.server.tsfiles to pass theBootstrapContextto thebootstrapApplicationcall.In addition,
getPlatform()anddestroyPlatform()will now returnnulland be a no-op respectively when running in a server environment.compiler-cli
core
BootstrapContextfor improved server bootstrapping (#63562)migrations
v21.0.0-next.2Compare Source
Breaking Changes
common
TestBednow provides a fakePlatformLocationimplementation that supports the Navigation API. This may break some
tests, though we have not observed any failures internally. You can revert to the
old default for
TestBedby providing theMockPlatformLocationfrom@angular/common/testingin your providers:{provide: PlatformLocation, useClass: MockPlatformLocation}core
provideZoneChangeDetectionin theTestBed providers would previously prevent
TestBedfrom rethrowingerrors as it should. Errors in the test will now be rethrown, regardless
of the usage of
provideZoneChangeDetection. Tests should be adjusted toprevent or account for these errors. As in previous major versions,
this behavior can be disabled with
rethrowApplicationErrors: falseinconfigureTestingModuleas a last resort.ignoreChangesOutsideZoneis no longer available as anoption for configuring ZoneJS change detection behavior.
platform-browser
ApplicationConfigexport from@angular/platform-browserhas been removed.Please import
ApplicationConfigfrom@angular/coreinstead.router
microtasks to complete. Tests have been found to often be highly
dependent on the exact timing of navigation completions with respect to
the microtask queue. The most common fix for tests is to ensure all
navigations have been completed before making assertions. On rare
occasions, this can also affect production applications. This can be
caused by multiple subscriptions to router state throughout the application,
both of which trigger navigations that happened to not conflict with the
previous timing.
upgrade
UpgradeAdapteris no longer available. Useupgrade/staticinsteadcommon
compiler
core
rxResourcestreamthrew before returning anObservable(#63342)forms
http
platform-browser
ApplicationConfigexport (#63529)platform-server
router
upgrade
v21.0.0-next.1Compare Source
Breaking Changes
common
forms
common
ngModuleFactoryinput ofNgComponentOutlet(#62838)compiler
core
@forloop animations never get cancelled (#63328)animate.leavebinding to a string with spaces (#63366)forms
migrations
v21.0.0-next.0Compare Source
Breaking Changes
compiler-cli
the
emitDeclarationOnlyTS compiler option is enabled as this mode isnot supported.
router
lastSuccessfulNavigationis now a signal and needs to be invokedcompiler-cli
emitDeclarationOnlyTS compiler option enabled (#61609)http
router
lastSuccessfulNavigationto signal (#63057)v20.3.1Compare Source
compiler
aria-invalid(#63748)compiler-cli
core
migrations
v20.3.0Compare Source
Breaking Changes
core
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
A schematic is provided to automatically update
main.server.tsfiles to pass theBootstrapContextto thebootstrapApplicationcall.In addition,
getPlatform()anddestroyPlatform()will now returnnulland be a no-op respectively when running in a server environment.(cherry picked from commit
8bf80c9)core
BootstrapContextfor improved server bootstrapping (#63636)angular/angular-cli (@angular/build)
v21.0.0-next.4Compare Source
@angular/build
v21.0.0-next.3Compare Source
Breaking Changes
@angular/build
@angular/ssr
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
@schematics/angular
@angular/cli
find_examplestool to a stable tool@angular-devkit/build-angular
@angular/build
@angular/ssr
v21.0.0-next.2Compare Source
@angular/cli
ng addfunctionalityConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.