This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/example/vite-react-app/multi-de36fa8f59
in repository https://gitbox.apache.org/repos/asf/ofbiz-plugins.git
omit f278a5697 Bump react-dom and @types/react-dom in
/example/vite-react-app
add a1bcd7bd0 Removed: obsolete screenxls-typed example demo view-maps and
UI entry points (OFBIZ-13578)
add ac32aafb0 Bump react and @types/react in /example/vite-react-app
add caa98ccc3 Bump react-dom and @types/react-dom in
/example/vite-react-app
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 (f278a5697)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/example/vite-react-app/multi-de36fa8f59
(caa98ccc3)
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:
example/vite-react-app/package-lock.json | 4 ++--
example/vite-react-app/package.json | 4 ++--
example/webapp/example/WEB-INF/controller.xml | 4 ----
example/widget/example/CommonScreens.xml | 3 ---
example/widget/example/ExampleForms.xml | 4 ----
5 files changed, 4 insertions(+), 15 deletions(-)
