build: update cross-repo angular dependencies #2177
+13,215
−15,771
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
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
from
e758ce6 to
b1871cd
Compare
angular-robot
changed the title
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
16 times, most recently
from
a7386db to
950c62a
Compare
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
8 times, most recently
from
9197463 to
696d4c1
Compare
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
3 times, most recently
from
7add060 to
384a2d3
Compare
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
18 times, most recently
from
4100de6 to
d47be69
Compare
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
10 times, most recently
from
bed367b to
4b9ad56
Compare
See associated pull request for more information.
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
from
4b9ad56 to
e636918
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.
This PR contains the following updates:
13.3.9->20.2.0-rc.018.1.0-rc.0->20.2.0-rc.018.2.10->20.2.0-rc.012.2.16->20.2.0-rc.013.3.9->20.2.0-rc.018.1.0-rc.0->20.2.0-rc.012.2.16->20.2.0-rc.013.3.9->20.2.0-rc.018.1.0-rc.0->20.2.0-rc.012.2.16->20.2.0-rc.0^20.0.0-rc.2->^20.2.0-rc13.3.9->20.2.0-rc.018.1.0-rc.0->20.2.0-rc.0^13.0.0->^20.2.0-rc18.2.10->20.2.0-rc.012.2.16->20.2.0-rc.0262cb3b->6d9c06920.2.0-next.6->20.2.0-rc.0f89362d->a7e9f67^18.0.0-next.0->^20.2.0-next🔡 If you wish to disable git hash updates, add
":disableDigestUpdates"to the extends array in your config.Release Notes
angular/angular (@angular/common)
v20.2.0-rc.0Compare Source
compiler-cli
core
asaliases onelse ifblocks (#63047)afterRenderEffect(#63001)@iftoggles with leave animations (#63048)router
service-worker
v20.2.0-next.6Compare Source
compiler-cli
v20.2.0-next.5Compare Source
Deprecations
router
platform-browser
router
v20.2.0-next.4Compare Source
Deprecations
router
compiler-cli
core
animate.enterclass removal when composing classes (#62981)fetchresponses when loading external resources in JIT (#62992)forms
http
set()inHttpResource(#62873)migrations
platform-browser
router
currentNavigationsignal to theRouterservice. (#62971)service-worker
v20.2.0-next.3Compare Source
Deprecations
animations
core
animations
compiler
compiler-cli
core
http
service-worker
v20.2.0-next.2Compare Source
compiler
compiler-cli
core
platform-browser
service-worker
v20.2.0-next.1Compare Source
compiler
compiler-cli
core
http
HttpClient(#62586)Angular detected that aHttpClientrequest with thekeepaliveoption was sent using XHRwhen option is not true (#62536)language-service
router
v20.2.0-next.0Compare Source
http
v20.1.6Compare Source
v20.1.5Compare Source
compiler-cli
core
fetchresponses when loading external resources in JIT (#62992)http
set()inHttpResource(#62873)migrations
v20.1.4Compare Source
compiler
core
http
v20.1.3Compare Source
core
platform-browser
v20.1.2Compare Source
compiler
v20.1.1Compare Source
compiler
compiler-cli
core
http
Angular detected that aHttpClientrequest with thekeepaliveoption was sent using XHRwhen option is not true (#62536)router
v20.1.0Compare Source
common
compiler
compiler-cli
core
destroyedproperty onDestroyRef(#61849)destroyedproperty toEnvironmentInjector(#61951)forms
FormGroup/FormRecord(#55860)http
language-service
router
loadComponentandloadChildrenfunctions in the route's injection context (#62133)service-worker
v20.0.7Compare Source
compiler-cli
v20.0.6Compare Source
v20.0.5Compare Source
compiler-cli
core
ErrorHandlerfrom a destroyed injector (#61886)router
upgrade
v20.0.4Compare Source
core
APP_IDbefore injector is destroyed (#61885)migrations
v20.0.3Compare Source
v20.0.2Compare Source
core
onDestroyinoutputToObservable(#61882)v20.0.1Compare Source
compiler
core
takeUntilDestroyedcompletes immediately if DestroyRef already destroyed (#61847)onDestroyinResourceImplwhendestroy()is called (#61870)onDestroywhen observable errors intoSignal(#61596)migrations
service-worker
v20.0.0Compare Source
Blog post: https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301
Breaking Changes
common
Yformatter (week-numbering year) without also includingw(week number) is now detected as suspicious date pattern, asyis typically intended.AsyncPipenow directly catches unhandled errors insubscriptions and promises and reports them to the application's
ErrorHandler. For Zone-based applications, these errors would havebeen caught by ZoneJS and reported to
ErrorHandlerso the result isgenerally the same. The change to the exact mechanism for reporting can
result in differences in test environments that will require test
updates.
compiler
'in' in an expression now refers to the operator
voidin an expression now refers to the operatorPreviously an expression in the template like
{{void}}referred to aproperty on the component class. After this change it now refers to the
voidoperator, which would make the above example invalid. If you haveexisting expressions that need to refer to a property named
void,change the expression to use
this.voidinstead:{{this.void}}.Parenthesis are always respected.
This can lead to runtime breakages when a nullish coalescing operator is nested within parentheses.
eg.
{{ (foo?.bar).baz }}will throw iffoois nullish. This is the same behavior as native JavaScript.core
TypeScript versions less than 5.8 are no longer supported.
the
TestBed.flushEffects()was removed - usethe
TestBed.tick()instead.provideExperimentalCheckNoChangesForDebughas severalbreaking changes:
provideCheckNoChangesConfiguseNgZoneOnStableoption is removed. This wasn't found to be generallymore useful than
intervalprovideExperimentalZonelessChangeDetectionisrenamed to
provideZonelessChangeDetectionas it is now "DeveloperPreview" rather than "Experimental".
InjectFlagshas been removed.injectno longer acceptsInjectFlags.Injector.getno longer acceptsInjectFlags.EnvironmentInjector.getno longer acceptsInjectFlags.TestBed.getno longer acceptsInjectFlags.TestBed.injectno longer acceptsInjectFlags.TestBed.gethas been removed. UseTestBed.injectinstead.afterRender was renamed to afterEveryRender.
Before upgrading to Angular v20, ensure the Node.js version is at least 20.11.1.
For the full list of supported versions, visit: https://angular.dev/reference/versions
PendingTasks.runno longer returns the result of theasync function. If this behavior is desired, it can be re-implemented
manually with the
PendingTasks.add. Be aware, however, that promise rejectionswill need to be handled or they can cause the node process to shut down
when using SSR.
Uncaught errors in listeners which were previously only reported to
ErrorHandlerare now also reported to Angular's internal errorhandling machinery. For tests, this means that the error will be
rethrown by default rather than only logging the error. Developers
should fix these errors, catch them in the test if the test is
intentionally covering an error case, or use
rethrowApplicationErrors: falseinconfigureTestingModuleas a last resort.The
anyoverload has been removed frominjector.get. It now only supportsProviderToken<T>and (deprecatedsince v4)
string.Animations are guaranteed to be flushed when Angular
runs automatic change detection or manual calls to
ApplicationRef.tick.Prior to this change, animations would not be flushed in some situations
if change detection did not run on any views attached to the
application. This change can affect tests which may rely on the old
behavior, often by making assertions on DOM elements that should have
been removed but weren't because DOM removal is delayed until animations
are flushed.
ApplicationRef.tickwill no longer catch and reporterrors to the appplication
ErrorHandler. Errors will instead be thrown out ofthe method and will allow callers to determine how to handle these
errors, such as aborting follow-up work or reporting the error and
continuing.
This commit deprecates
ng-reflect-*attributes and updates the runtime to stop producing them by default. Please refactor application and test code to avoid relying onng-reflect-*attributes.To enable a more seamless upgrade to v20, we've added the
provideNgReflectAttributes()function (can be imported from the@angular/corepackage), which enables the mode in which Angular would be producing those attribites (in dev mode only). You can add theprovideNgReflectAttributes()function to the list of providers within the bootstrap call.router
RedirectFncan now returnObservableorPromise. Any code that directly calls functions returning this typemay need to be adjusted to account for this.
required writable arrays have now been updated to accept readonly
arrays when no mutations are done.
Routeno longer includeanyinthe type union. The union includes functions for the functional guards
as well as a type matching
Injector.get:ProviderToken<T>|string.Note that string is still deprecated on both the route guards and
Injector.get.Deprecations
core
ngIf/ngFor/ngSwitchare deprecated. Use the control flow blocks instead (@for/@if/@switch).platform-browser
@angular/platform-browser-dynamicplatform-server
@angular/platform-server/testingUse e2e tests to verify SSR behavior instead.
common
updateLatestValueif view is destroyed before promise resolves (#58041)Configuration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.