This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/angular/animations-21.2.11
in repository https://gitbox.apache.org/repos/asf/fineract-backoffice-ui.git
discard 4344334 chore(deps): bump @angular/animations from 20.3.18 to 21.2.11
add 77d138c chore(deps): bump fast-uri from 3.1.0 to 3.1.2
add 3cd5a2a Merge pull request #50 from
apache/dependabot/npm_and_yarn/fast-uri-3.1.2
add bee583a chore(deps): bump ip-address and express-rate-limit
add 7f1228d Merge pull request #48 from
apache/dependabot/npm_and_yarn/multi-7bdfbe8666
add 2bf22c0 chore(deps): bump @angular/animations from 20.3.18 to 21.2.12
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 (4344334)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/angular/animations-21.2.11 (2bf22c0)
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 | 30 +++++++++++++++---------------
package.json | 2 +-
2 files changed, 16 insertions(+), 16 deletions(-)
