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:
570ce43
->d5c7341
19.0.0-next.6
->19.0.0-next.7
7c83b9a
->f46197a
2b8a271
->3571818
c4e14e5
->da2cc94
19.0.0-next.6
->19.0.0-next.7
ac6ec8f
->f789e0f
19.0.0-next.6
->19.0.0-next.7
bc1999d
->90cc8da
19.0.0-next.6
->19.0.0-next.7
714325a
->b6a407c
19.0.0-next.6
->19.0.0-next.7
bbba10f
->35579f6
19.0.0-next.6
->19.0.0-next.7
1568920
->3a3db66
da5fbd4
->0ba126c
19.0.0-next.6
->19.0.0-next.7
cd6632e
->b606b78
70dfc3a
->be0bf8e
9794cd2
->39e1a11
f4cbe66
->9e883e2
19.0.0-next.6
->19.0.0-next.7
4893259
->fd4b165
19.0.0-next.6
->19.0.0-next.7
8b96985
->3b935b4
19.0.0-next.6
->19.0.0-next.7
f0ae27f
->c78a769
19.0.0-next.6
->19.0.0-next.7
6b1b7e9
->1ebb25b
19.0.0-next.6
->19.0.0-next.7
5b6bd65
->0bf58af
🔡 If you wish to disable git hash updates, add
":disableDigestUpdates"
to the extends array in your config.Release Notes
angular/angular (@angular/animations)
v19.0.0-next.7
Compare Source
Breaking Changes
core
Changes to effect timing which generally has two implications:
effects which are triggered outside of change detection run as part of
the change detection process instead of as a microtask. Depending on the
specifics of application/test setup, this can result in them executing
earlier or later (or requiring additional test steps to trigger; see below
examples).
effects which are triggered during change detection (e.g. by input
signals) run earlier, before the component's template.
We've seen a few common failure cases:
Tests which used to rely on the
Promise
timing of effects now need toawait whenStable()
or call.detectChanges()
in order for effects torun.
Tests which use faked clocks may need to fast-forward/flush the clock to
cause effects to run.
effect()
s triggered during CD could rely on the application being fullyrendered (for example, they could easily read computed styles, etc). With
the change, they run before the component's updates and can get incorrect
answers. The recent
afterRenderEffect()
API is a natural replacement forthis style of effect.
effect()
s which synchronize with the forms system are particularlytiming-sensitive and might need to adjust their initialization timing.
ExperimentalPendingTasks
has been renamed toPendingTasks
.core
allowSignalWrites
(#57874)ViewContext
is retained after closure minification (#57903)language-service
Configuration
📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, 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.