-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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 #55806
Closed
angular-robot
wants to merge
1
commit into
angular:main
from
angular-robot:ng-renovate/cross-repo-angular-dependencies
Closed
build: update cross-repo angular dependencies #55806
angular-robot
wants to merge
1
commit into
angular:main
from
angular-robot:ng-renovate/cross-repo-angular-dependencies
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
angular-robot
added
action: merge
The PR is ready for merge by the caretaker
area: build & ci
Related the build and CI infrastructure of the project
target: patch
This PR is targeted for the next patch release
labels
May 15, 2024
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
from
May 15, 2024 21:05
bbe42aa
to
3fd0b52
Compare
angular-robot
changed the title
build: update cross-repo angular dependencies to v18.0.0-rc.2
build: update cross-repo angular dependencies
May 15, 2024
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
12 times, most recently
from
May 22, 2024 21:06
010e44f
to
7f0f8df
Compare
pkozlowski-opensource
added
action: cleanup
The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews
and removed
action: merge
The PR is ready for merge by the caretaker
labels
May 23, 2024
This update causes real test failures so will need to be updated / cleaned up before it can be merged. |
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
from
May 23, 2024 15:07
7f0f8df
to
de274dc
Compare
josephperrott
pushed a commit
to josephperrott/angular
that referenced
this pull request
May 23, 2024
See associated pull request for more information. Closes angular#55806 as a pr takeover
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
5 times, most recently
from
May 27, 2024 18:05
0aeb085
to
5a32af7
Compare
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
3 times, most recently
from
May 28, 2024 13:08
7523f1b
to
33c2127
Compare
josephperrott
pushed a commit
to josephperrott/angular
that referenced
this pull request
May 28, 2024
See associated pull request for more information. Closes angular#55806 as a pr takeover
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
2 times, most recently
from
May 29, 2024 17:06
aa8d2ba
to
bb67bfb
Compare
josephperrott
pushed a commit
to josephperrott/angular
that referenced
this pull request
May 29, 2024
See associated pull request for more information. Closes angular#55806 as a pr takeover
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
2 times, most recently
from
May 29, 2024 20:06
7a88cf8
to
4dd4e3c
Compare
See associated pull request for more information.
angular-robot
force-pushed
the
ng-renovate/cross-repo-angular-dependencies
branch
from
May 30, 2024 03:05
4dd4e3c
to
4d3f0fd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
action: cleanup
The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews
area: build & ci
Related the build and CI infrastructure of the project
target: patch
This PR is targeted for the next patch release
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:
^0.1800.0-next
->^0.1801.0-next
18.0.0-rc.2
->18.1.0-next.0
17.3.7
->18.0.2
18.0.0-rc.2
->18.1.0-next.0
18.0.0-rc.2
->18.1.0-next.0
^18.0.0-next
->^18.1.0-next
17.3.8
->18.0.1
18.0.0-rc.2
->18.1.0-next.0
8b5a565
->6dc56ea
18.0.0-rc.1
->18.1.0-next.0
18.0.0-rc.2
->18.1.0-next.0
17.3.7
->18.0.2
17.3.8
->18.0.1
17.3.8
->18.0.1
17.3.8
->18.0.1
^17.0.0
->^18.0.0
17.3.8
->18.0.1
c4a61e9
->93e7e56
17.3.8
->18.0.1
17.3.8
->18.0.1
17.3.8
->18.0.1
18.0.0-rc.1
->18.1.0-next.0
347f73d
->68feef7
17.3.8
->18.0.1
17.3.8
->18.0.1
17.3.8
->18.0.1
17.3.8
->18.0.1
17.3.8
->18.0.1
17.3.7
->18.0.2
17.3.8
->18.0.1
18.0.0-rc.2
->18.1.0-next.0
89624a6
->e805b4c
π‘ 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.1801.0-next.0
Compare Source
v0.1800.2
Compare Source
v0.1800.1
Compare Source
v0.1800.0
Compare Source
v0.1800.0-rc.3
Compare Source
v0.1800.0-rc.2
Compare Source
angular/angular (@βangular/animations)
v18.1.0-next.0
Compare Source
core
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)v18.0.0-rc.3
Compare Source
18.0.0-rc.3 (2024-05-21)
compiler
compiler-cli
@if
with aliases (#β55835)core
service-worker
controllerchange
listener when app is destroyed (#β55365)v18.0.0-rc.2
Compare Source
18.0.0-rc.2 (2024-05-15)
core
@Component.interpolation
(#β55778)forms
migrations
Deprecations
core
@Component.interpolation
is deprecated. Use Angular'sdelimiters instead.
v18.0.0-rc.1
Compare Source
18.0.0-rc.1 (2024-05-08)
compiler
core
http
withRequestsMadeViaParent
behavior withwithFetch
(#β55652)migrations
platform-browser
platform-server
angular/components (@βangular/cdk)
v18.1.0-next.0
Compare Source
v18.0.1
Compare Source
material
youtube-player
v18.0.0
Compare Source
Breaking Changes
material
ng update
, your app will be fixed automatically.define-light-theme
tom2-define-light-theme
define-dark-theme
tom2-define-dark-theme
define-palette
tom2-define-palette
get-contrast-color-from-palette
tom2-get-contrast-color-from-palette
get-color-from-palette
tom2-get-color-from-palette
get-color-config
tom2-get-color-config
get-typography-config
tom2-get-typography-config
get-density-config
tom2-get-density-config
$red-palette
to$m2-red-palette
$pink-palette
to$m2-pink-palette
$indigo-palette
to$m2-indigo-palette
$purple-palette
to$m2-purple-palette
$deep-purple-palette
to$m2-deep-purple-palette
$blue-palette
to$m2-blue-palette
$light-blue-palette
to$m2-light-blue-palette
$cyan-palette
to$m2-cyan-palette
$teal-palette
to$m2-teal-palette
$green-palette
to$m2-green-palette
$light-green-palette
to$m2-light-green-palette
$lime-palette
to$m2-lime-palette
$yellow-palette
to$m2-yellow-palette
$amber-palette
to$m2-amber-palette
$orange-palette
to$m2-orange-palette
$deep-orange-palette
to$m2-deep-orange-palette
$brown-palette
to$m2-brown-palette
$grey-palette
to$m2-grey-palette
$gray-palette
to$m2-gray-palette
$blue-grey-palette
to$m2-blue-grey-palette
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.
π» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.