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.0
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard 73c2a46 chore: bump ts-jest from 29.1.4 to 29.4.0
add 4f130ab chore: bump eslint from 9.28.0 to 9.29.0 (#160)
add c832a93 chore: bump @types/node from 22.15.21 to 24.0.3 (#161)
add 16e2169 chore: Add shfmt and shellcheck linters (#158)
add cd47366 chore: bump google-closure-compiler from 20250603.0.0 to
20250609.0.0 (#163)
add 274b46b chore: Use Node.js 20 (#156)
add 1966a64 chore: bump ts-jest from 29.1.4 to 29.4.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 (73c2a46)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/ts-jest-29.4.0
(1966a64)
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/test.sh => .editorconfig | 20 +--
.env | 2 +-
.github/workflows/test.yaml | 8 +-
.pre-commit-config.yaml | 17 +++
.github/ISSUE_TEMPLATE/config.yml => .shellcheckrc | 3 +-
ci/scripts/build.sh | 4 +-
dev/release/release.sh | 2 +-
dev/release/verify_rc.sh | 20 +--
package.json | 8 +-
yarn.lock | 143 +++++++++++----------
10 files changed, 127 insertions(+), 100 deletions(-)
copy ci/scripts/test.sh => .editorconfig (73%)
mode change 100755 => 100644
copy .github/ISSUE_TEMPLATE/config.yml => .shellcheckrc (94%)
