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.35.0
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard aae5f49 chore: bump eslint from 9.34.0 to 9.35.0
add 7f6d61d chore: Use apache/arrow-dotnet for integration test (#269)
add 8e4e3a1 chore: bump typedoc from 0.28.11 to 0.28.12 (#271)
add 5de306f chore: bump google-closure-compiler from 20250820.0.0 to
20250903.0.0 (#275)
add 929bb89 chore: bump eslint from 9.34.0 to 9.35.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 (aae5f49)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/eslint-9.35.0
(929bb89)
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 | 6 ++
package.json | 4 +-
yarn.lock | 134 ++++++++++++++++++++++----------------------
3 files changed, 75 insertions(+), 69 deletions(-)
