build: update angular dependencies #2343
Closed
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:
19.0.0-next.6->19.0.0-next.719.0.0-next.5->19.0.0-next.619.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.719.0.0-next.5->19.0.0-next.619.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.719.0.0-next.6->19.0.0-next.7Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
angular/angular (@angular/animations)
v19.0.0-next.7Compare 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
Promisetiming 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.
ExperimentalPendingTaskshas been renamed toPendingTasks.core
allowSignalWrites(#57874)ViewContextis retained after closure minification (#57903)language-service
angular/components (@angular/cdk)
v19.0.0-next.6Compare Source
cdk
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: 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.