This is an automated email from the ASF dual-hosted git repository.

dependabot[bot] pushed a change to branch dependabot/npm_and_yarn/glob-13.0.6
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git


    omit 73327b5  chore(deps): bump glob from 11.1.0 to 13.0.6
     add c75aeed  chore(deps): bump actions/setup-java from 5.7.0 to 6.0.0 
(#362)
     add 5cb73fb  chore(deps): bump the gh-actions-patch-minor group with 2 
updates (#361)
     add cad19f5  chore(deps): bump @xmldom/xmldom from 0.8.13 to 0.8.15 (#363)
     add 07c74ec  chore(deps-dev): bump browserslist from 4.24.2 to 4.28.8 
(#364)
     add 49a5cf9  chore(deps): bump the gh-actions-patch-minor group with 3 
updates (#366)
     add 9ad6d69  chore(deps-dev): bump js-yaml from 3.14.2 to 3.15.2 (#365)
     add b72f35a  chore(deps-dev): bump nyc from 17.1.0 to 18.0.0 (#359)
     add 7a9eb6e  chore(deps): bump glob from 11.1.0 to 13.0.6

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   (73327b5)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/glob-13.0.6 
(7a9eb6e)

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/ci.yml |   6 +-
 package-lock.json        | 291 ++++++++++++++++++++++++++++++-----------------
 package.json             |   2 +-
 3 files changed, 189 insertions(+), 110 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to