This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/npm_and_yarn/typescript-5.8.3
in repository https://gitbox.apache.org/repos/asf/arrow-js.git
discard 8502fe5 chore: bump typescript from 5.4.5 to 5.8.3
add 685399d chore: Run Release Audit Tool in CI (#129)
add 958dab9 chore: bump @swc/helpers from 0.5.15 to 0.5.17 (#131)
add c9ee085 chore: bump typescript-eslint from 8.32.1 to 8.33.1 (#132)
add b810d7e chore: bump typescript from 5.4.5 to 5.8.3
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 (8502fe5)
\
N -- N -- N refs/heads/dependabot/npm_and_yarn/typescript-5.8.3
(b810d7e)
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/test.yaml | 26 ++-
.gitignore | 5 +
.npmrc | 17 ++
ci/scripts/test.sh => .pre-commit-config.yaml | 27 +--
dev/release/check_rat_report.py | 59 +++++++
.../release/rat_exclude_files.txt | 4 +-
dev/release/run_rat.sh | 54 ++++++
package.json | 2 +-
yarn.lock | 184 +++++++++------------
9 files changed, 253 insertions(+), 125 deletions(-)
copy ci/scripts/test.sh => .pre-commit-config.yaml (64%)
mode change 100755 => 100644
create mode 100755 dev/release/check_rat_report.py
copy .github/ISSUE_TEMPLATE/config.yml => dev/release/rat_exclude_files.txt
(93%)
create mode 100755 dev/release/run_rat.sh
