This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/web-streams-polyfill-4.2.0
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard a72740a chore: bump web-streams-polyfill from 3.2.1 to 4.2.0
add 3b5de98 chore: bump google-closure-compiler from 20250810.0.0 to
20250813.0.0 (#246)
add 2c88adb chore: bump @swc-node/register from 1.10.10 to 1.11.1 (#247)
add 5b09a92 chore: bump rollup from 4.46.2 to 4.46.3 (#253)
add 28408be chore: bump @types/node from 24.2.1 to 24.3.0 (#252)
add d7d8394 chore: bump typescript-eslint from 8.39.1 to 8.40.0 (#251)
add 678b618 chore: bump web-streams-polyfill from 3.2.1 to 4.2.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 (a72740a)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/web-streams-polyfill-4.2.0 (678b618)
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 | 8 +-
yarn.lock | 726 +++++++++++++++++++++++++++++++----------------------------
2 files changed, 386 insertions(+), 348 deletions(-)
