-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore(deps): update @angular to v18 #126
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/@angular
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
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
renovate
bot
force-pushed
the
renovate/@angular
branch
from
March 14, 2020 14:00
3aa875f
to
8d01ab5
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
April 29, 2020 21:04
88b52e8
to
560984e
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
3 times, most recently
from
May 13, 2020 22:31
9b32c58
to
972ceca
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
May 21, 2020 00:17
82a8ec5
to
62702ce
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
June 10, 2020 18:25
973fb4d
to
1e9222b
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
June 24, 2020 22:51
1e9222b
to
00bfe9c
Compare
renovate
bot
changed the title
chore(deps): update @angular to v9
chore(deps): update @angular to v10
Jun 24, 2020
renovate
bot
force-pushed
the
renovate/@angular
branch
from
June 26, 2020 20:31
00bfe9c
to
7d7c439
Compare
renovate
bot
changed the title
chore(deps): update @angular to v10
chore(deps): update @angular
Jun 26, 2020
renovate
bot
force-pushed
the
renovate/@angular
branch
from
June 26, 2020 20:34
7d7c439
to
9318198
Compare
renovate
bot
changed the title
chore(deps): update @angular
chore(deps): update @angular to v10
Jun 26, 2020
renovate
bot
force-pushed
the
renovate/@angular
branch
from
July 1, 2020 22:54
9318198
to
5532b68
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
July 10, 2020 16:00
5532b68
to
7524988
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
August 22, 2020 04:02
7524988
to
79e822e
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
October 29, 2020 09:01
79e822e
to
6387ac5
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
November 26, 2020 23:54
6387ac5
to
bdb1e6a
Compare
renovate
bot
changed the title
chore(deps): update @angular to v10
chore(deps): update @angular to v11
Nov 26, 2020
renovate
bot
force-pushed
the
renovate/@angular
branch
from
December 10, 2020 07:01
bdb1e6a
to
24b5658
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
January 10, 2021 00:00
347c722
to
eb030fa
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
January 22, 2021 07:52
eb030fa
to
80db07b
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
February 1, 2021 09:57
80db07b
to
19ac141
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
February 11, 2021 11:08
a148452
to
910bb38
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
April 26, 2021 17:17
910bb38
to
91f5b3e
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
May 22, 2024 22:48
6276353
to
39fa20a
Compare
renovate
bot
changed the title
chore(deps): update @angular to v17
chore(deps): update @angular to v18
May 22, 2024
renovate
bot
force-pushed
the
renovate/@angular
branch
from
May 29, 2024 17:08
39fa20a
to
6c9c39e
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
June 5, 2024 22:27
6c9c39e
to
8d05b39
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
June 13, 2024 02:45
8d05b39
to
2ef4138
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
June 27, 2024 07:23
122a424
to
2e4b5d4
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
July 10, 2024 14:15
ec12ccb
to
cb679eb
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
July 24, 2024 19:27
b2401f1
to
786d501
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
August 6, 2024 08:08
be3ba9b
to
e0d7c73
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
3 times, most recently
from
August 14, 2024 18:35
8824dc4
to
987c2a5
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
3 times, most recently
from
August 29, 2024 00:03
7c909eb
to
9a1ad8f
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
September 4, 2024 16:29
9a1ad8f
to
e59d045
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
September 18, 2024 16:15
3f276b7
to
b8cbbc3
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
2 times, most recently
from
October 2, 2024 15:32
561cf65
to
a9c7bf8
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
October 10, 2024 10:16
a9c7bf8
to
0ac3b2e
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
3 times, most recently
from
October 30, 2024 19:47
9264905
to
8809d63
Compare
renovate
bot
force-pushed
the
renovate/@angular
branch
from
November 6, 2024 21:36
8809d63
to
43d35b5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
~7.2.15
->~18.2.11
Release Notes
angular/angular (@angular/animations)
v18.2.11
Compare Source
core
v18.2.10
Compare Source
compiler
localize
v18.2.9
Compare Source
compiler-cli
v18.2.8
Compare Source
compiler
compiler-cli
core
platform-server
PlatformRef
when error happens during thebootstrap()
phase (#58112) (#58135)v18.2.7
Compare Source
common
compiler-cli
core
http
migrations
upgrade
v18.2.6
Compare Source
v18.2.5
Compare Source
compiler-cli
core
@let
declaration with array whenpreparingForHydration
(#57816)migrations
v18.2.4
Compare Source
compiler
migrations
v18.2.3
Compare Source
http
v18.2.2
Compare Source
core
http
router
upgrade
v18.2.1
Compare Source
core
fakeAsync
(#56932)migrations
v18.2.0
Compare Source
Breaking Changes
zone.js
fakeAsync
will now flush pending timers at the end ofthe given function by default. To opt-out of this, you can use
{flush: false}
in options parameter offakeAsync
compiler
compiler-cli
interpolatedSignalNotInvoked
extended diagnostic (#57291)core
v18.1.5
Compare Source
compiler-cli
core
v18.1.4
Compare Source
compiler
compiler-cli
interpolatedSignalNotInvoked
extended diagnostic (#57291)language-service
v18.1.3
Compare Source
compiler
compiler-cli
core
v18.1.2
Compare Source
compiler
compiler-cli
core
afterNextRender
hooks return that callback value. (#57031)v18.1.1
Compare Source
v18.1.0
Compare Source
common
compiler
compiler-cli
core
toSignal
(#56447)ComponentMirror
(#56402)afterRender
&afterNextRender
phases API (#55648)forms
NgControlStatus
host bindingsOnPush
compatible (#55720)http
Content-Type
header case insensitive (#56541)language-service
router
UrlTree
as an input torouterLink
(#56265)v18.0.7
Compare Source
compiler
http
fetch
outside of Angular zone (#56820)migrations
v18.0.6
Compare Source
common
core
router
v18.0.5
Compare Source
core
@defer
error. (#56559)v18.0.4
Compare Source
compiler-cli
core
router
v18.0.3
Compare Source
benchpress
core
localize
@angular/localize/init
as polyfill inangular.json
(#56300)migrations
v18.0.2
Compare Source
core
HttpClientModule
imports on components. (#56067)withI18nSupport()
call for components that use i18n blocks (#56175)migrations
v18.0.1
Compare Source
compiler
compiler-cli
core
migrations
v18.0.0
Compare Source
Blog post "Angular v18 is now available".
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
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 4am every weekday,every weekend" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.