Open
Conversation
d982211 to
a0b5949
Compare
a0b5949 to
3392be1
Compare
c8853ae to
fc47ae2
Compare
32a75cc to
f78b75c
Compare
f7fc9d2 to
a7364e8
Compare
343c451 to
43a654d
Compare
999614d to
bb86bc4
Compare
38a1a34 to
cdc242d
Compare
cdc242d to
910971e
Compare
07e3d91 to
ab6a2fd
Compare
69b1695 to
8e3e19e
Compare
8e3e19e to
fe1d66c
Compare
3a04baf to
4a7ad82
Compare
f013cb1 to
e3c6bdb
Compare
e3c6bdb to
bfb5007
Compare
3695004 to
f3d0769
Compare
991160f to
a2530cc
Compare
e0a8c36 to
f42545f
Compare
f8496a3 to
7eea70c
Compare
fe244f0 to
cba7aed
Compare
cba7aed to
ec32e53
Compare
300bfd6 to
48149c8
Compare
a49119b to
331a823
Compare
331a823 to
7efed8e
Compare
6037e77 to
765b85b
Compare
765b85b to
51a8aae
Compare
b59e172 to
e5828b4
Compare
aa3c9c3 to
2d65d1f
Compare
716b24d to
9881f90
Compare
9881f90 to
00daf06
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:
15.2.10→21.1.315.2.10→21.1.315.2.10→21.1.315.2.10→21.1.315.2.10→21.1.315.2.10→21.1.3Release Notes
angular/angular (@angular/common)
v21.1.3Compare Source
core
linkedSignal.updateshould propagate errorsforms
localize
router
v21.1.2Compare Source
forms
language-service
router
v21.1.1Compare Source
compiler-cli
core
forms
v21.1.0Compare Source
Deprecations
upgrade
VERSIONfrom@angular/upgradeis deprecated. Please use the entry from@angular/upgrade/staticinstead.common
compiler
core
StaticProviderforprovidePlatformInitializerforms
platform-browser
contexttocreateApplicationcreateApplicationrouter
upgrade
VERSIONexportv21.0.9Compare Source
forms
migrations
v21.0.8Compare Source
core
v21.0.7Compare Source
compiler
compiler-cli
importsexpressiontypeoftype referencescore
forms
[formField]directivedirtyinputhiddeninputpendinginputrouter
queryParamsHandlingupdateCallbackDonepromisev21.0.6Compare Source
Breaking Changes (affecting only experimental features)
forms
The shape of
SignalFormsConfig.classeshas changedPreviously each function in the
classesmap took aFieldState. Nowit takes a
Fielddirective.For example if you previously had:
You would need to update to:
(cherry picked from commit
348f149)(cherry picked from commit
ae0c590)core
forms
language-service
v21.0.5Compare Source
core
InjectionTokenwith factory onlyforms
v21.0.4Compare Source
compiler
compiler-cli
forms
Fielddirectivev21.0.3Compare Source
compiler-cli
core
[field]binding instructions (#65599)forms
FormUiControlsignals[field]bindings (#65599)http
router
v21.0.2Compare Source
compiler
attributeNameand MathML/SVG URLsv21.0.1Compare Source
compiler-cli
core
platformBrowserDynamicDOCUMENTforCSP_NONCEforms
Fielddirectivetypebindings on signal form controlshttp
migrations
v21.0.0Compare Source
Blog post "Announcing Angular v21".
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}ngComponentOutletContentis now of typeNode[][] | undefinedinstead ofany[][] | undefined.compiler-cli
"typeCheckHostBindings": falsein theangularCompilerOptionssection of your tsconfig.the
emitDeclarationOnlyTS compiler option is enabled as this mode isnot supported.
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.Using a combination of
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.
(test only) - Using
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.
Angular no longer provides a change detection scheduler
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.The
interpolationoption on Components has been removed. Only the default{{ ... }}is now supported.elements
Fix signal input getter behavior in custom elements.
Before this change, signal inputs in custom elements required function calls to access their values (
elementRef.newInput()), while decorator inputs were accessed directly (elementRef.oldInput). This inconsistency caused confusion and typing difficulties.The getter behavior has been standardized so signal inputs can now be accessed directly, matching the behavior of decorator inputs:
Before:
elementRef.oldInputelementRef.newInput()After:
elementRef.oldInputelementRef.newInputforms
platform-browser
ApplicationConfigexport from@angular/platform-browserhas been removed.Please import
ApplicationConfigfrom@angular/coreinstead.router
lastSuccessfulNavigationis now a signal and needs to be invokedmicrotasks 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/staticinsteadzone.js
Deprecations
http
HttpResponseBase.statusTextis deprecatedcommon
ngComponentOutletContent(#63674)ngModuleFactoryinput ofNgComponentOutlet(#62838)compiler
compiler-cli
@defertriggers (#64069)emitDeclarationOnlyTS compiler option enabled (#61609)core
bootstrapModuleoptions (#64354)BootstrapContextfor improved server bootstrapping (#63562)@foriteration over field is reactive (#64113)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.
🔕 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.