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

dependabot[bot] pushed a change to branch dependabot/npm_and_yarn/eslint-10.13.0
in repository https://gitbox.apache.org/repos/asf/arrow-js.git


    omit 23f9a242 chore: bump eslint from 9.39.2 to 10.13.0
     add 9fb0e2d6 chore: bump markdown-it from 14.3.2 to 14.3.3 (#516)
     add 11e3b878 chore: bump actions/setup-python from 7.0.0 to 7.1.0 (#517)
     add a77db761 chore: bump rollup from 4.63.5 to 4.65.0 (#518)
     add 367ba63a chore: bump eslint-plugin-jest from 29.15.0 to 29.17.0 (#519)
     add dc60434d chore: bump eslint from 9.39.2 to 10.13.0

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   (23f9a242)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/eslint-10.13.0 
(dc60434d)

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/test.yaml |   4 +-
 package-lock.json           | 224 ++++++++++++++++++++++----------------------
 package.json                |   4 +-
 3 files changed, 116 insertions(+), 116 deletions(-)

Reply via email to