Skip to content

fix(crypto): deprecate events field in shielded TRC20 scan APIs #192

fix(crypto): deprecate events field in shielded TRC20 scan APIs

fix(crypto): deprecate events field in shielded TRC20 scan APIs #192

Triggered via pull request April 21, 2026 04:09
Status Success
Total duration 16m 43s
Artifacts 2

pr-build.yml

on: pull_request
Build debian11 (JDK 8 / x86_64)
16m 14s
Build debian11 (JDK 8 / x86_64)
Coverage Base (JDK 8 / x86_64)
16m 17s
Coverage Base (JDK 8 / x86_64)
Build ubuntu24 (JDK 17 / aarch64)
13m 44s
Build ubuntu24 (JDK 17 / aarch64)
Build rockylinux (JDK 8 / x86_64)
16m 18s
Build rockylinux (JDK 8 / x86_64)
Matrix: build-macos
Coverage Gate
19s
Coverage Gate
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
Coverage Gate
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
Coverage Gate
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
Build ubuntu24 (JDK 17 / aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build macos26 (JDK 17 / aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build debian11 (JDK 8 / x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Coverage Base (JDK 8 / x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build rockylinux (JDK 8 / x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Coverage Gate
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: madrapps/jacoco-report@v1.7.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
jacoco-coverage-base
451 KB
sha256:79bf27a80c6f4e7a1ce892660a9a9bfdecbbf4da4441cb243adb060e77da5d49
jacoco-coverage-pr
452 KB
sha256:c208090b94e8f62ddb270f3f9f1a69048ed12ba1b42d3e078aa812a5f66e575a