This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/npm_and_yarn/gulp-5.0.1
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
omit 5404090 chore: bump gulp from 4.0.2 to 5.0.1
add 2ab6f4b chore: bump rollup from 4.43.0 to 4.44.0 (#177)
add 714c4e3 chore: bump eslint-plugin-jest from 28.9.0 to 29.0.1 (#178)
add 0289e92 chore: Fix auto documentation update (#173)
add e91bf1e chore: bump typescript-eslint from 8.33.1 to 8.35.0 (#174)
add aff7891 chore: bump @swc/core from 1.11.31 to 1.12.5 (#179)
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 0c27104 chore: bump gulp from 4.0.2 to 5.0.1
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 (5404090)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/gulp-5.0.1
(0c27104)
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:
ci/scripts/update_docs.sh | 4 +-
package.json | 12 +-
yarn.lock | 612 +++++++++++++++++++++++-----------------------
3 files changed, 314 insertions(+), 314 deletions(-)
