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

github-bot pushed a change to branch dependabot/npm_and_yarn/cross-env-10.1.0
in repository https://gitbox.apache.org/repos/asf/arrow-js.git


 discard aee75f6  chore: bump cross-env from 10.0.0 to 10.1.0
     add 2c753fc  chore: bump webpack from 5.101.3 to 5.102.0 (#292)
     add 3b2c73d  chore: bump actions/cache from 4.2.4 to 4.3.0 (#290)
     add b745480  chore: bump typescript-eslint from 8.43.0 to 8.45.0 (#291)
     add d6010ec  chore: bump eslint from 9.35.0 to 9.36.0 (#289)
     add 5d2519f  chore: Bump version to 21.1.0 (#297)
     add 356a399  chore: bump memfs from 4.39.0 to 4.48.1 (#301)
     add f2b9d67  chore: bump @types/node from 24.5.2 to 24.7.0 (#304)
     add e656bcc  chore: bump google-closure-compiler from 20250903.0.0 to 
20251001.0.0 (#303)
     add f454a35  chore: bump typescript-eslint from 8.45.0 to 8.46.1 (#306)
     add 870e27e  chore: bump del from 8.0.0 to 8.0.1 (#307)
     add 3461c94  chore: bump cross-env from 10.0.0 to 10.1.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   (aee75f6)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/cross-env-10.1.0 
(3461c94)

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 |  10 +-
 package.json                |  14 +-
 yarn.lock                   | 378 +++++++++++++++++++++++---------------------
 3 files changed, 207 insertions(+), 195 deletions(-)

Reply via email to