chore(deps): bump @angular/core from 19.0.5 to 19.1.1 in /frontend in the npm_and_yarn group across 1 directory #997
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.
Bumps the npm_and_yarn group with 1 update in the /frontend directory: @angular/core.
Updates
@angular/core
from 19.0.5 to 19.1.1Release notes
Sourced from
@angular/core
's releases.... (truncated)
Changelog
Sourced from
@angular/core
's changelog.... (truncated)
Commits
357795c
fix(core): run HMR replacement in the zone (#59562)74daef1
refactor(core): move logic out of shared instructions code (#59453)3e7ba3d
docs: set syntax highlighting to the remaining Markdown code examples blocks ...a7f824a
fix(core): destroy renderer when replacing styles during HMR (#59514)e33e673
refactor(core): do not serialize parent block id for top level blocks (#59190)03339d5
refactor(core): change node navigation step to plain const (#59469)6fc5f18
test(migrations): add test for earlier fix (#59497)59a1d68
fix(migrations): incorrect stats when migrating queries with best effort mode...ca1d392
test: add test to verify extending tsconfig works in signal input migration (...7debf0f
test: improve typescript version coverage for signal input migration (#59463)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.