Skip to content

修复在支持 IP Range Ban 能力的下载器版本上的 IPV4MappedIPV6Address 特殊地址的问题 #1770 #8429

修复在支持 IP Range Ban 能力的下载器版本上的 IPV4MappedIPV6Address 特殊地址的问题 #1770

修复在支持 IP Range Ban 能力的下载器版本上的 IPV4MappedIPV6Address 特殊地址的问题 #1770 #8429

Triggered via push April 6, 2026 10:42
Status Success
Total duration 9m 58s
Artifacts 11

jvm-ci.yml

on: push
Build JAR Files  /  ...  /  Build WebUI
1m 28s
Build JAR Files / WebUI / Build WebUI
Build Standalone Docker Images
3m 55s
Build Standalone Docker Images
Build JAR Files  /  Gradle
1m 38s
Build JAR Files / Gradle
Generate Installers  /  install4jc
4m 32s
Generate Installers / install4jc
Matrix: Generate FreeBSD Package / pkg
Generate Synology Package  /  pkgcreate
2m 44s
Generate Synology Package / pkgcreate
Generate Debian Package  /  dpkg
20s
Generate Debian Package / dpkg
Build and Push Docker Images
3m 42s
Build and Push Docker Images
Generate Portable Version  /  dpkg
28s
Generate Portable Version / dpkg
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build JAR Files / WebUI / Build WebUI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@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 JAR Files / Test
No files were found with the provided path: build/reports/tests/ build/test-results/. No artifacts will be uploaded.
Build Standalone Docker Images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.19.2, docker/metadata-action@v5.10.0, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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 and Push Docker Images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.19.2, docker/login-action@v3, docker/metadata-action@v5.10.0, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Generate Installers / install4jc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: luangong/setup-install4j@v1. 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
PBH-BTN~PeerBanHelper~AM5UZR.dockerbuild
76 KB
sha256:6cbd1bd904e5950def10bc402280c3625ca6017e9b7cac3bdab08fb345d65710
PBH-BTN~PeerBanHelper~WL59M8.dockerbuild
113 KB
sha256:5af2a4c9e5f3d38ec2fda9ddc96a27891c153ab1a5b57565ad6d72c29a29aa54
deb-dist
67.9 MB
sha256:43709c50964824dffb0626e1306e6f942ba7d57798f4a9a3d0337b4e45d4dd58
freebsd-pkg-13.4-dist
67.9 MB
sha256:aec31f6f6fcb727705fc1d740501e6535e958a2bf72fcd3d22d2d393f3e2154b
freebsd-pkg-14.1-dist
67.9 MB
sha256:9defaa2e898b3e9ce6e925fb9dff8ab06106a364b79695367fc9274b36065c04
gradle-dist
69 MB
sha256:ffcd8e0d837d4712fbfeb4c27cfef9ca579bc8565396bd12748fe60b85196de5
installer-dist
1.2 GB
sha256:cd6739c29a84ea3cd0e650db3ed46639e4e1764ffb70a7326eb3d24cb3d22f72
jbr-dist
50.3 MB
sha256:a4a2ce9490f72c956e9ceba7e724bce2a4e85764c2342c314f7eea92a1556781
portable-dist
264 MB
sha256:b1cd42fd071e55425dfe212faf7a303c8c6918c63f7c99f2f0087c14f225147f
spk-dist
269 KB
sha256:2b64dac4a84e5a48286648f14049ce9aace6159fd0ae3e79411f80782d213247
webui-dist
5.56 MB
sha256:e3cf681c26dd43bb43c2244f9c27785cf0f69fdfcf705cf759df61b67d8c450a