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/release24.09/types/react-dom-19.2.5
in repository https://gitbox.apache.org/repos/asf/ofbiz-plugins.git
discard 7bd66b565 Bump @types/react-dom from 19.2.4 to 19.2.5 in
/example/vite-react-app
add 36001478c Bump org.apache.tomcat.embed:tomcat-embed-websocket in
/example
add ee3e717fd Bump io.swagger.core.v3:swagger-jaxrs2-servlet-initializer
in /rest-api
add 5ca9c09b0 Bump @vitejs/plugin-react from 6.0.5 to 6.1.0 in
/example/vite-react-app
add 920e816a7 Bump @types/react-dom from 19.2.4 to 19.2.5 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 (7bd66b565)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/example/vite-react-app/release24.09/types/react-dom-19.2.5
(920e816a7)
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/build.gradle | 2 +-
example/vite-react-app/package-lock.json | 12 ++++++++----
example/vite-react-app/package.json | 2 +-
rest-api/build.gradle | 6 +++---
4 files changed, 13 insertions(+), 9 deletions(-)
