-
Notifications
You must be signed in to change notification settings - Fork 0
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 to v18 (major) #61
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-angular-monorepo
base: master
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.
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/major-angular-monorepo
branch
from
November 18, 2020 18:44
c812f8b
to
4e84a78
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v11 (major)
fix(deps): update angular monorepo (major)
Nov 18, 2020
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
November 18, 2020 18:48
4e84a78
to
a620b63
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo (major)
fix(deps): update angular monorepo to v11 (major)
Nov 18, 2020
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
November 19, 2020 19:53
a620b63
to
d3dd10f
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
December 2, 2020 18:35
d3dd10f
to
7c190e7
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
January 10, 2021 13:53
e9abeb7
to
ff16e84
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
January 23, 2021 09:59
ff16e84
to
a03a92e
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
January 30, 2021 19:05
a03a92e
to
1e7f63f
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
February 11, 2021 11:11
2656475
to
5185c32
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
April 26, 2021 16:05
5185c32
to
7c3d465
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
May 15, 2021 20:13
3911676
to
ce17748
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v11 (major)
fix(deps): update angular monorepo to v12 (major)
May 15, 2021
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 6, 2021 19:52
ce17748
to
b41881d
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 15, 2021 02:14
b41881d
to
fb4bc9f
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
October 18, 2021 20:58
fb4bc9f
to
ccbdec9
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
March 7, 2022 17:56
ccbdec9
to
8025e60
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v12 (major)
fix(deps): update angular monorepo to v13 (major)
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
March 26, 2022 15:17
8025e60
to
4c7dccd
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
April 25, 2022 02:34
4c7dccd
to
4ef9c4b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 15, 2022 21:37
4ef9c4b
to
64397c1
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 18, 2022 20:14
64397c1
to
5a67ecb
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v13 (major)
fix(deps): update angular monorepo to v14 (major)
Jun 18, 2022
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 23, 2022 19:57
5a67ecb
to
20efc32
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
September 25, 2022 17:56
20efc32
to
df80868
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
March 16, 2023 07:29
df80868
to
d691e2c
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v14 (major)
fix(deps): update angular monorepo to v15 (major)
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
December 21, 2023 17:05
799252d
to
fe12ab7
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
January 10, 2024 22:25
fe12ab7
to
757ca25
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
January 24, 2024 19:48
aa51391
to
740b525
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
January 31, 2024 22:47
740b525
to
e8d67f0
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
February 15, 2024 01:11
9fdf056
to
bbb2360
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
February 28, 2024 01:00
8940a55
to
bbd7a70
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
March 6, 2024 20:29
bbd7a70
to
ba22557
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
March 20, 2024 20:15
a6a1839
to
e304636
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
April 3, 2024 23:18
c854758
to
b078b4b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
April 17, 2024 18:35
11bd858
to
f7f12d5
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
May 2, 2024 02:13
f73debe
to
1f19d66
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 8, 2024 16:26
1f19d66
to
eb29d8b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
May 22, 2024 21:51
809e813
to
0434be2
Compare
renovate
bot
changed the title
fix(deps): update angular monorepo to v17 (major)
fix(deps): update angular monorepo to v18 (major)
May 22, 2024
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 29, 2024 19:32
0434be2
to
45a1a9c
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 5, 2024 21:40
45a1a9c
to
8cedccb
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 13, 2024 01:05
8cedccb
to
13716f2
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 20, 2024 22:13
13716f2
to
8949888
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:
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
10.1.4
->18.0.4
Release Notes
angular/angular (@angular/animations)
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
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)v17.3.11
Compare Source
17.3.11 (2024-06-05)
v17.3.10
Compare Source
v17.3.9
Compare Source
v17.3.8
Compare Source
compiler
core
v17.3.7
Compare Source
v17.3.6
Compare Source
core
ActivatedRoute
inject correct instance inside@defer
blocks (#55374)v17.3.5
Compare Source
v17.3.4
Compare Source
common
v17.3.3
Compare Source
17.3.3 (2024-04-03)
core
ChainedInjector
s in injector debug utils (#55144)migrations
v17.3.2
Compare Source
compiler
compiler-cli
core
@defer
blocks (#55079)http
migrations
router
v17.3.1
Compare Source
17.3.1 (2024-03-20)
compiler
compiler-cli
v17.3.0
Compare Source
compiler
compiler-cli
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 has been generated by Mend Renovate. View repository job log here.