build: update cross-repo angular dependencies to v22#262
Open
angular-robot wants to merge 1 commit intoangular:mainfrom
Open
build: update cross-repo angular dependencies to v22#262angular-robot wants to merge 1 commit intoangular:mainfrom
angular-robot wants to merge 1 commit intoangular:mainfrom
Conversation
f1d7cfc to
f473471
Compare
c8c11b0 to
2a06543
Compare
69e568e to
4b2d53c
Compare
4b2d53c to
ecd4911
Compare
Contributor
Author
|
a989841 to
f5dd03e
Compare
bf237ee to
501b710
Compare
d6466b9 to
cd86ef6
Compare
27bf190 to
ccbc3ff
Compare
ccbc3ff to
893d453
Compare
893d453 to
20f3f6e
Compare
See associated pull request for more information.
20f3f6e to
7d145b9
Compare
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
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:
^21.2.0-next→^22.0.0-next21.2.0-next.2→22.0.0-next.5^21.2.0-next→^22.0.0-next21.2.0-next.4→22.0.0-next.4^21.2.0-next→^22.0.0-next21.2.0-next.2→22.0.0-next.5^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next21.2.0-next.3→22.0.0-next.721.2.0-next.3→22.0.0-next.7^21.2.0-next→^22.0.0-next21.2.0-next.2→22.0.0-next.5Release Notes
angular/angular (@angular/animations)
v22.0.0-next.7Compare Source
Breaking Changes
core
anyanymore. Make sure the element you pass is not nullable.ComponentFactoryResolverandComponentFactoryare no longer available. Pass the component class directly to APIs that previously required a factory, such asViewContainerRef.createComponentor use the standalonecreateComponentFunction.ComponentFactoryResolverandComponentFactoryare no longer available. Pass the component class directly to APIs that previously required a factory, such asViewContainerRef.createComponentor use the standalonecreateComponentfunction.platform-browser
host. However other DOM on the page may still be affected by those styles if not leveragingViewEncapsulation.Emulatedor if those styles are used by elements outside of Angular, potentially causing other DOM to appear unstyled.router
currentSnapshotparameter inCanMatchFnand thecanMatchmethod of theCanMatchinterface is now required. While this was already the behavior of the Router at runtime, existing class implementations ofCanMatchmust now include the third argument to satisfy the interface.compiler
compiler-cli
core
ApplicationRefwith configforms
language-service
migrations
platform-browser
hostis droppedrouter
v22.0.0-next.6Compare Source
compiler
compiler-cli
core
object[data]as resource URL context (#67797)localize
migrations
router
v22.0.0-next.5Compare Source
Breaking Changes
compiler-cli
core
changeDetectionproperty are nowOnPushby default. SpecifychangeDetection: ChangeDetectionStrategy.Eagerto keep the previous behavior.platform-browser
common
compiler
compiler-cli
core
forms
reloadValidationto Signal Forms to manually trigger async validationto`FormRootto be used without submission options (#67727)migrations
platform-browser
v22.0.0-next.4Compare Source
Breaking Changes
core
ChangeDetectorRef.checkNoChangeswas removed. In tests usefixture.detectChanges()instead.compiler
compiler-cli
core
checkNoChangesfrom the public API.forms
language-service
migrations
router
optionsoptional parameter forwithComponentInputBindingservice-worker
v22.0.0-next.3Compare Source
compiler
core
v22.0.0-next.2Compare Source
Breaking Changes
core
createNgModuleRefwas removed, usecreateNgModuleinsteadcore
toString()representationcreateNgModuleRefforms
SignalFormsConfigto a readonly APIlanguage-service
v22.0.0-next.1Compare Source
compiler
compiler-cli
forms
migrations
v22.0.0-next.0Compare Source
Breaking Changes
compiler
invariables will throw in template expressions.core
http
HttpXhrBackendwithprovideHttpClient(withXhr)if you want to keep supporting upload progress reports.router
provideRoutes()has been removed. UseprovideRouter()orROUTESas multi token if necessary.upgrade
getAngularLib/setAngularLibhave been removed usegetAngularJSGlobal/setAngularJSGlobalinstead.Deprecations
http
withFetchis now deprecated, it can be safely removed.compiler
data-attributescompiler-cli
core
IdleRequestOptionssupport toIdleServiceprovideHttpClientto keep using theHttpXhrBackendimplementation.ChangeDetectionStrategy.Eagerwhere applicableforms
touchedmodel into an input andtouchoutputsetValuein reactive formshttp
FetchBackendas default for theHttpBackendimplementationlanguage-service
| Commit