generated from esm-bundle/autopublish-template
-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update angular monorepo to v18 (major) #190
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-angular-monorepo
base: main
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/major-angular-monorepo
branch
2 times, most recently
from
May 10, 2023 18:16
bf6f737
to
3ab7507
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
May 17, 2023 22:18
7baffc2
to
78b593b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 24, 2023 18:20
78b593b
to
666a124
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
June 1, 2023 19:29
57f6dc4
to
d978d54
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
June 14, 2023 20:05
80b1b3e
to
3d0a5a5
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
June 28, 2023 17:19
aa4087f
to
f0e9966
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 29, 2023 00:58
f0e9966
to
0507bff
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 7, 2023 00:40
85422e8
to
b88d92e
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 19, 2023 20:03
3a40b89
to
1128abb
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
July 26, 2023 18:22
1128abb
to
8bf6183
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
August 2, 2023 19:59
8bf6183
to
a149f45
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 16, 2023 18:27
2c8178a
to
ad5f5e2
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 24, 2023 18:49
ce57e72
to
a10aad5
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
August 30, 2023 19:12
a10aad5
to
49bbea1
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
September 13, 2023 18:23
afa5eff
to
1546b77
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
September 20, 2023 18:23
1546b77
to
23ff65b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
September 27, 2023 23:01
23ff65b
to
091249b
Compare
|
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 22, 2024 21:53
d6a35b7
to
16b2192
Compare
renovate
bot
changed the title
Update angular monorepo to v17 (major)
Update angular monorepo to v18 (major)
May 22, 2024
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 29, 2024 19:39
16b2192
to
f1efcfd
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 5, 2024 22:44
f1efcfd
to
c8496de
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
June 13, 2024 00:52
c8496de
to
e3e7a35
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
June 27, 2024 00:24
cf4dafb
to
dfc1cd8
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 10, 2024 14:26
c09f176
to
74187c4
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 24, 2024 21:05
7719231
to
858c3eb
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
July 31, 2024 18:45
858c3eb
to
1790b75
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 14, 2024 17:59
83aeb23
to
a1eb0fe
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 28, 2024 22:32
96d969e
to
5b778dc
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
September 4, 2024 15:49
5b778dc
to
e6d0f6b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
September 18, 2024 19:10
6716817
to
4a3a41f
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
October 2, 2024 13:24
e6fbbfb
to
25def84
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
October 10, 2024 12:26
d325e01
to
fcd3615
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
October 30, 2024 21:07
8ddad09
to
0d1f463
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
November 6, 2024 18:54
0d1f463
to
bccbfee
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:
15.2.10
->18.2.11
15.2.10
->18.2.11
15.2.10
->18.2.11
15.2.10
->18.2.11
15.2.10
->18.2.11
15.2.10
->18.2.11
15.2.10
->18.2.11
Release Notes
angular/angular (@angular/common)
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
jit: true
opt-out (#56892)@NgModule
classes withjit: true
(#57212)core
language-service
migrations
router
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
platformDynamicServer
has been removed. Add an `import @&#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.