This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/test/babel/core-7.18.13
in repository https://gitbox.apache.org/repos/asf/incubator-flagon-useralejs.git
discard b437a6a Bump @babel/core from 7.18.10 to 7.18.13
add 41479c2 updates package dependencies
add 760f66c updates package dependencies /example/webpack
add 534ff9f Merge pull request #279 from poorejc/master
add 36150c6 Bump @babel/core from 7.18.10 to 7.18.13
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 (b437a6a)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/test/babel/core-7.18.13 (36150c6)
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/webpackUserAleExample/dist/main.js | 8 +-
example/webpackUserAleExample/package-lock.json | 851 +++++++++++-------------
example/webpackUserAleExample/package.json | 4 +-
package.json | 8 +-
4 files changed, 415 insertions(+), 456 deletions(-)
