This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/ts-jest-29.4.11
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard efe8b92 chore: bump ts-jest from 29.1.4 to 29.4.11
add cbc3074 chore: bump command-line-usage from 7.0.3 to 7.0.4 (#443)
add f2ad02f chore: bump markdown-it from 14.1.0 to 14.2.0 (#447)
add 2e68d2a chore: bump actions/checkout from 6.0.3 to 7.0.0 (#448)
add 12a0332 chore: bump @swc/helpers from 0.5.19 to 0.5.23 (#449)
add 5933ec1 chore: bump actions/cache from 5.0.5 to 6.1.0 (#451)
add 31bfd19 chore: bump actions/setup-python from 6.2.0 to 6.3.0 (#452)
add 936e283 chore: bump typedoc from 0.28.17 to 0.28.19 (#453)
add aaca904 chore: bump ts-jest from 29.1.4 to 29.4.11
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 (efe8b92)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/ts-jest-29.4.11
(aaca904)
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/rc.yaml | 10 ++--
.github/workflows/release.yaml | 2 +-
.github/workflows/test.yaml | 36 ++++++-------
package-lock.json | 116 +++++++++++++++++++++++++++--------------
package.json | 2 +-
5 files changed, 101 insertions(+), 65 deletions(-)
