This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/npm_and_yarn/eslint-9.30.0
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard 55ca481 chore: bump eslint from 9.29.0 to 9.30.0
add d4033c5 chore: bump gulp-rename from 2.0.0 to 2.1.0 (#182)
add 0d914d4 chore: bump google-closure-compiler from 20250619.0.0 to
20250625.0.0 (#183)
add c8b3fd4 chore: bump eslint from 9.29.0 to 9.30.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 (55ca481)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/eslint-9.30.0
(c8b3fd4)
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:
package.json | 4 ++--
yarn.lock | 76 ++++++++++++++++++++++++++++++------------------------------
2 files changed, 40 insertions(+), 40 deletions(-)
