This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/app/launch/vitejs/plugin-react-6.0.4
in repository https://gitbox.apache.org/repos/asf/grails-forge-ui.git
discard f6bb1f7 Bump @vitejs/plugin-react from 6.0.1 to 6.0.4 in /app/launch
add 116dbaf Batch dependency updates
add cd8104d Merge pull request #148 from apache/deps/batch-updates
add ad67399 Bump @vitejs/plugin-react from 6.0.3 to 6.0.4 in /app/launch
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 (f6bb1f7)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/app/launch/vitejs/plugin-react-6.0.4
(ad67399)
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:
.github/workflows/gradle.yml | 6 +-
.github/workflows/publish.yml | 6 +-
app/launch/package-lock.json | 1183 ++++++++++++++++++++---------------------
app/launch/package.json | 16 +-
4 files changed, 603 insertions(+), 608 deletions(-)
