This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/npm_and_yarn/ts-jest-29.4.6
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard f244746 chore: bump ts-jest from 29.1.4 to 29.4.6
add 6baf26e chore: bump actions/checkout from 6.0.0 to 6.0.1 (#349)
add 9ec4fc4 chore: bump actions/cache from 4.3.0 to 5.0.1 (#352)
add 08c17f1 chore: bump actions/upload-artifact from 5.0.0 to 6.0.0 (#353)
add c1f214c chore: bump actions/download-artifact from 6.0.0 to 7.0.0
(#354)
add ac672de chore: bump typescript-eslint from 8.49.0 to 8.50.0 (#355)
add 124c502 chore: bump @rollup/plugin-alias from 5.1.1 to 6.0.0 (#356)
add 04944d4 chore: bump ts-jest from 29.1.4 to 29.4.6
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 (f244746)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/ts-jest-29.4.6
(04944d4)
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 | 20 +++---
.github/workflows/release.yaml | 2 +-
.github/workflows/test.yaml | 32 ++++-----
package.json | 4 +-
yarn.lock | 150 ++++++++++++++++++++---------------------
5 files changed, 104 insertions(+), 104 deletions(-)
