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
fix(deps): update angular monorepo #83
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/angular-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
✅ Deploy Preview for plugin-angular-universal-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
November 15, 2023 21:33
8a5bf6f
to
3e27080
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.2
fix(deps): update angular monorepo to v17.0.3
Nov 15, 2023
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
November 20, 2023 22:38
3e27080
to
eeaf9f1
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.3
fix(deps): update angular monorepo to v17.0.4
Nov 20, 2023
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
November 29, 2023 18:19
eeaf9f1
to
59bf70d
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.4
fix(deps): update angular monorepo to v17.0.5
Nov 29, 2023
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
December 6, 2023 18:53
59bf70d
to
0301880
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.5
fix(deps): update angular monorepo to v17.0.6
Dec 6, 2023
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
December 14, 2023 17:45
0301880
to
bd75eb5
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.6
fix(deps): update angular monorepo to v17.0.7
Dec 14, 2023
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
December 21, 2023 17:24
bd75eb5
to
2150ea6
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.7
fix(deps): update angular monorepo to v17.0.8
Dec 21, 2023
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
January 10, 2024 06:00
2150ea6
to
fac786f
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.0.8
fix(deps): update angular monorepo
Jan 10, 2024
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
January 11, 2024 00:13
fac786f
to
08e665f
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
January 24, 2024 21:26
ec245ca
to
1dc7df1
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
January 31, 2024 19:43
1dc7df1
to
aeb829a
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo
fix(deps): update angular monorepo - autoclosed
Feb 2, 2024
renovate
bot
changed the title
fix(deps): update angular monorepo - autoclosed
fix(deps): update angular monorepo
Feb 8, 2024
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
February 8, 2024 21:25
aeb829a
to
06e0c8e
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo
fix(deps): update angular monorepo to v17.1.3
Feb 8, 2024
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
February 13, 2024 22:47
06e0c8e
to
f2373cb
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17.1.3
fix(deps): update angular monorepo
Feb 13, 2024
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
February 15, 2024 00:20
d053cb3
to
415e4f5
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
February 28, 2024 00:45
753c888
to
8d2d728
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
March 6, 2024 21:30
8d2d728
to
605d9bc
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
March 20, 2024 21:03
29622b4
to
04cd16a
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
April 4, 2024 01:55
b4f6d77
to
0bee452
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
April 17, 2024 18:50
fcdefd4
to
1d6c20e
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
April 25, 2024 18:26
f2afd83
to
bf6127a
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
2 times, most recently
from
May 2, 2024 02:23
5f1688b
to
500af83
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
May 8, 2024 20:16
500af83
to
575441e
Compare
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
3 times, most recently
from
May 22, 2024 13:57
1b993af
to
20d6069
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo
fix(deps): update dependency zone.js to v0.14.6
May 22, 2024
renovate
bot
force-pushed
the
renovate/angular-monorepo
branch
from
May 22, 2024 19:02
20d6069
to
48bf196
Compare
renovate
bot
changed the title
fix(deps): update dependency zone.js to v0.14.6
fix(deps): update angular monorepo
May 22, 2024
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:
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
18.0.0-rc.3
->18.0.0
0.14.3
->0.14.6
Release Notes
angular/angular (@angular/animations)
v18.0.0
Compare Source
Breaking Changes
animations
matchesElement
method has been removed fromAnimationDriver
as it is unused.common
isPlatformWorkerUi
andisPlatformWorkerApp
have been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.compiler
compiler-cli
core
OnPush
views at the root of the application need tobe marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush
change detection strategy.OnPush
views at the root of the application need tobe marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush
change detection strategy.The
ComponentFixture
autoDetect
feature will nolonger refresh the component's host view when the component is
OnPush
and not marked dirty. This exposes existing issues in components which
claim to be
OnPush
but do not correctly callmarkForCheck
when theyneed to be refreshed. If this change causes test failures, the easiest
fix is to change the component to
ChangeDetectionStrategy.Default
.ComponentFixture.whenStable
now matches theApplicationRef.isStable
observable. Prior to this change, stabilityof the fixture did not include everything that was considered in
ApplicationRef
.whenStable
of the fixture will now include unfinishedrouter navigations and unfinished
HttpClient
requests. This will causetests that
await
thewhenStable
promise to time out when there areincomplete requests. To fix this, remove the
whenStable
,instead wait for another condition, or ensure
HttpTestingController
mocks responses for all requests. Try adding
HttpTestingController.verify()
before your
await fixture.whenStable
to identify the open requests.Also, make sure your tests wait for the stability promise. We found many
examples of tests that did not, meaning the expectations did not execute
within the test body.
In addition,
ComponentFixture.isStable
would synchronously switch totrue in some scenarios but will now always be asynchronous.
Angular will ensure change detection runs, even when the state update originates from
outside the zone, tests may observe additional rounds of change
detection compared to the previous behavior.
This change will be more likely to impact existing unit tests.
This should usually be seen as more correct and the test should be updated,
but in cases where it is too much effort to debug, the test can revert to the old behavior by adding
provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
to the
TestBed
providers.Similarly, applications which may want to update state outside the zone
and not trigger change detection can add
provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
to the providers in
bootstrapApplication
or addschedulingMode: NgZoneSchedulingMode.NgZoneOnly
to theBootstrapOptions
ofbootstrapModule
.When Angular runs change detection, it will continue to
refresh any views attached to
ApplicationRef
that are still marked forcheck after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges
. This will be surfaced as a runtimeerror with the
NG0103
code.async
has been removed, usewaitForAsync
instead.The
ComponentFixture.autoDetect
feature now executeschange detection for the fixture within
ApplicationRef.tick
. This moreclosely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to
ApplicationRef
(i.e. dialog components).Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with
NgZone
is now the first of eithersetTimeout
orrequestAnimationFrame
. Code which relies on thistiming (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend
afterNextRender
instead of something like
setTimeout
.Newly created and views marked for check and reattached
during change detection are now guaranteed to be refreshed in that same
change detection cycle. Previously, if they were attached at a location
in the view tree that was already checked, they would either throw
ExpressionChangedAfterItHasBeenCheckedError
or not be refreshed untilsome future round of change detection. In rare circumstances, this
correction can cause issues. We identified one instance that relied on
the previous behavior by reading a value on initialization which was
queued to be updated in a microtask instead of being available in the
current change detection round. The component only read this value during
initialization and did not read it again after the microtask updated it.
Testability methods
increasePendingRequestCount
,decreasePendingRequestCount
andgetPendingRequestCount
have beenremoved. This information is tracked with zones.
http
By default we now prevent caching of HTTP requests that require authorization . To opt-out from this behaviour use the
includeRequestsWithAuthHeaders
option inwithHttpTransferCache
.Example:
platform-browser
StateKey
,TransferState
andmakeStateKey
have been removed from@angular/platform-browser
, use the same APIs from@angular/core
.platform-browser-dynamic
RESOURCE_CACHE_PROVIDER
APIs have been removed.platform-server
deprecated
platformDynamicServer
has been removed. Add animport @​angular/compiler
and replace the usage withplatformServer
deprecated
ServerTransferStateModule
has been removed.TransferState
can be use without providing this module.deprecated
useAbsoluteUrl
andbaseUrl
been removed fromPlatformConfig
. Provide and absoluteurl
instead.Legacy handling or Node.js URL parsing has been removed from
ServerPlatformLocation
.The main differences are;
pathname
is always suffixed with a/
.port
is empty whenhttp:
protocol and port in url is80
port
is empty whenhttps:
protocol and port in url is443
router
RedirectCommand
for redirectsin addition to
UrlTree
. Code which expects onlyboolean
orUrlTree
values in
Route
types will need to be adjusted.Route.redirectTo
to be a functionin addition to the previous string. Code which expects
redirectTo
toonly be a string on
Route
objects will need to be adjusted.UrlTree
as a redirect, theredirecting navigation will now use
replaceUrl
if the initialnavigation was also using the
replaceUrl
option. If this is notdesirable, the redirect can configure new
NavigationBehaviorOptions
byreturning a
RedirectCommand
with the desired options instead ofUrlTree
.come from the injector heirarchy of the routes and never inherit from
the
RouterOutlet
. This means that providers available only to thecomponent that defines the
RouterOutlet
will no longer be available toroute components in any circumstances. This was already the case
whenever routes defined providers, either through lazy loading an
NgModule
or through explicitproviders
on the route config.come from the injector heirarchy of the routes and never inherit from
the
RouterOutlet
. This means that providers available only to thecomponent that defines the
RouterOutlet
will no longer be available toroute components in any circumstances. This was already the case
whenever routes defined providers, either through lazy loading an
NgModule
or through explicitproviders
on the route config.Deprecations
common
getCurrencySymbol
,getLocaleCurrencyCode
,getLocaleCurrencyName
,getLocaleCurrencySymbol
,getLocaleDateFormat
,getLocaleDateTimeFormat
,getLocaleDayNames
,getLocaleDayPeriods
,getLocaleDirection
,getLocaleEraNames
,getLocaleExtraDayPeriodRules
,getLocaleExtraDayPeriods
,getLocaleFirstDayOfWeek
,getLocaleId
,getLocaleMonthNames
,getLocaleNumberFormat
,getLocaleNumberSymbol
,getLocalePluralCase
,getLocaleTimeFormat
,getLocaleWeekEndRange
,getNumberOfCurrencyDigits
core
@Component.interpolation
is deprecated. Use Angular'sdelimiters instead.
http
HttpClientModule
,HttpClientXsrfModule
andHttpClientJsonpModule
As mentionned, those modules can be replaced by provider function only.
animations
matchesElement
fromAnimationDriver
(#55479)common
isPlatformWorkerApp
andisPlatformWorkerUi
API (#55302)compiler
FatalDiagnosticError
, hide themessage
field without affecting the emit (#55160)compiler-cli
@if
with aliases (#55835)core
ApplicationRef.tick
should respect OnPush for host bindings (#53718)ApplicationRef.tick
should respect OnPush for host bindings (#53718) (#53718)ComponentFixture
autoDetect
respectsOnPush
flag of host view (#54824)ComponentFixture
stability should matchApplicationRef
(#54949)async
function (#55491)setTimeout
andrAF
references (#55124)addEvent
(#55353)markForCheck
during change detection from causing infinite loops (#54900)@Component.interpolation
(#55778)forms
http
withRequestsMadeViaParent
behavior withwithFetch
(#55652)HttpClientModule
& related modules (#54020)language-service
migrations
HttpClientModule
(#54020)platform-browser
platform-browser-dynamic
RESOURCE_CACHE_PROVIDER
API has been removed (#54875)platform-server
nonce
attribute to event record script (#55495)platformDynamicServer
API (#54874)ServerTransferStateModule
API (#54874)useAbsoluteUrl
andbaseUrl
fromPlatformConfig
(#54874)router
withNavigationErrorHandler
can convert errors to redirects (#55370)UrlTree
withNavigationBehaviorOptions
from guards (#45023)RedirectCommand
(#54556)RouterOutlet
EnvironmentInjector
(#54265)RouterOutlet
EnvironmentInjector
(#54265)service-worker
controllerchange
(#54222)controllerchange
listener when app is destroyed (#55365)angular/angular (zone.js)
v0.14.6
Compare Source
Bug Fixes
fs
patch (#54396) (9e07b62)zone-patch-rxjs
(#55826) (20a530a), closes #55825abort
listener on a signal when actual event is removed (#55339) (a9460d0), closes #54739v0.14.5
Compare Source
Bug Fixes
v0.14.4
Compare Source
Bug Fixes
__Zone_ignore_on_properties
toZoneGlobalConfigurations
(#50737) (f87f058)fs.realpath.native
as macrotask (#54208) (19fae76), closes #45546Response
methods returned byfetch
(#50653) (260d3ed), closes #50327Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 Mend Renovate. View repository job log here.