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
build: update cross-repo angular dependencies #54891
build: update cross-repo angular dependencies #54891
Conversation
bec06e3
to
642c411
Compare
71b1324
to
2c0683b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
2c0683b
to
062682e
Compare
See associated pull request for more information.
062682e
to
2450eee
Compare
This PR was merged into the repository by commit b67e11a. |
Partial revert of angular#54891. Webcontainers do not support node ^18.19.1 which is required by the v18 CLI. Until this is solved by the stackblitz team, we're stucked with v17 based tutorials
Partial revert of angular#54891. Webcontainers do not support node ^18.19.1 which is required by the v18 CLI. Until this is solved by the stackblitz team, we're stucked with v17 based tutorials
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This PR contains the following updates:
^0.1703.0-rc
->^0.1800.0-next
17.3.0-rc.0
->18.0.0-next.3
17.2.3
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.3.0-rc.0
->18.0.0-next.3
17.3.0-rc.0
->18.0.0-next.3
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
bcdfe8a
->5b1b7bc
17.3.0-rc.0
->18.0.0-next.5
^17.3.0-rc
->^18.0.0-next
17.3.0-rc.0
->18.0.0-next.3
17.2.3
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
769e0bc
->1201678
17.2.4
->17.3.5
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
17.3.0-rc.0
->18.0.0-next.5
^17.3.0-rc
->^18.0.0-next
0720624
->43caa47
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
17.2.4
->17.3.5
17.2.4
->17.3.5
^17.3.0-rc
->^18.0.0-next
17.2.4
->17.3.5
17.2.3
->17.3.5
17.2.4
->17.3.5
17.3.0-rc.0
->18.0.0-next.3
1421ff0
->f122b83
π‘ If you wish to disable git hash updates, add
":disableDigestUpdates"
to the extends array in your config.Release Notes
angular/angular-cli (@βangular-devkit/architect-cli)
v0.1800.0-next.3
Compare Source
v0.1800.0-next.2
Compare Source
v0.1800.0-next.1
Compare Source
v0.1800.0-next.0
Compare Source
v0.1703.5
Compare Source
v0.1703.4
Compare Source
angular/angular (@βangular/animations)
v18.0.0-next.5
Compare Source
Breaking Changes
common
isPlatformWorkerUi
andisPlatformWorkerApp
have been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.compiler
core
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
.Testability methods
increasePendingRequestCount
,decreasePendingRequestCount
andgetPendingRequestCount
have beenremoved. This information is tracked with zones.
common
isPlatformWorkerApp
andisPlatformWorkerUi
API (#β55302)compiler
core
addEvent
(#β55353)service-worker
controllerchange
(#β54222)v18.0.0-next.4
Compare Source
common
compiler
language-service
v18.0.0-next.3
Compare Source
Breaking Changes
router
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.compiler
FatalDiagnosticError
, hide themessage
field without affecting the emit (#β55160)compiler-cli
core
setTimeout
andrAF
references (#β55124)ChainedInjector
s in injector debug utils (#β55144)forms
language-service
migrations
platform-browser
router
RedirectCommand
(#β54556)RouterOutlet
EnvironmentInjector
(#β54265)v18.0.0-next.2
Compare Source
Breaking Changes
compiler-cli
core
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.
router
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
.compiler
compiler-cli
core
ComponentFixture
stability should matchApplicationRef
(#β54949)@defer
blocks (#β55079)http
language-service
migrations
router
v18.0.0-next.1
Compare Source
Breaking Changes
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
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.compiler
compiler-cli
core
markForCheck
during change detection from causing infinite loops (#β54900)platform-browser-dynamic
RESOURCE_CACHE_PROVIDER
API has been removed (#β54875)platform-server
platformDynamicServer
API (#β54874)ServerTransferStateModule
API (#β54874)useAbsoluteUrl
andbaseUrl
fromPlatformConfig
(#β54874)router
v18.0.0-next.0
Compare Source
Breaking Changes
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.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
.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.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.
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
.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.
router
RedirectCommand
for redirectsin addition to
UrlTree
. Code which expects onlyboolean
orUrlTree
values in
Route
types will need to be adjusted.compiler-cli
core
ApplicationRef.tick
should respect OnPush for host bindings (#β53718) (#β53718)ComponentFixture
autoDetect
respectsOnPush
flag of host view (#β54824)router
UrlTree
withNavigationBehaviorOptions
from guards (#β45023)v17.3.5
Compare Source
v17.3.4
Compare Source
common
angular/components (@βangular/cdk)
v18.0.0-next.5
Compare Source
cdk
material
google-maps
v18.0.0-next.4
Compare Source
cdk
material
v18.0.0-next.3
Compare Source
material
multiple
v18.0.0-next.2
Compare Source
cdk
material
material-experimental
v18.0.0-next.1
Compare Source
cdk
v18.0.0-next.0
Compare Source
material
v17.3.5
Compare Source
cdk
material
google-maps
v17.3.4
Compare Source
cdk
material
v17.3.3
Compare Source
material
multiple
v17.3.2
Compare Source
cdk
material
v17.3.1
Compare Source
cdk
v17.3.0
Compare Source
material
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: Never, 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 Renovate Bot.