This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/angular/core-22.1.3
in repository https://gitbox.apache.org/repos/asf/fineract-backoffice-ui.git
discard 475efec build(deps): bump @angular/core from 22.1.0 to 22.1.3
add 1d7f400 fix(fintech): translate asset owner table titles
add f5f88b9 Merge pull request #471 from jaredrainsha/fix/251-fintech-i18n
add 0b6a341 build(deps-dev): bump karma-jasmine-html-reporter from 2.2.0
to 2.3.0
add 465ff6a Merge pull request #467 from
apache/dependabot/npm_and_yarn/karma-jasmine-html-reporter-2.3.0
add d1ab3e7 build(deps): bump @angular/core from 22.1.0 to 22.1.3
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (475efec)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/angular/core-22.1.3 (d1ab3e7)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
package-lock.json | 10 +++++-----
package.json | 2 +-
.../fintech/asset-owner-view/asset-owner-view.component.ts | 2 +-
src/app/features/fintech/asset-owners-list.component.ts | 2 +-
src/assets/i18n/en.json | 1 +
5 files changed, 9 insertions(+), 8 deletions(-)
