[stable33] fix: normalize missing bruteforce_protection and headers_to_exclude on ExApp routes #3475
oleksandr-nctests-deploy.yml
on: pull_request
NC In Host
1m 40s
NC In Julius Docker
2m 41s
NC In Julius Docker(DSP-HTTP)
1m 56s
NC In Julius Docker(DSP-HTTPS)
1m 48s
NC In Host(Redis)
2m 7s
NC In Host(network=host)
1m 34s
NC In Julius Docker (HaRP-Bridge network)
1m 47s
NC In Julius Docker (HaRP-Bridge network-no FRP TLS)
1m 53s
NC In Host (HaRP-Host network)
2m 9s
NC In Host (Manual HaRP-Host network)
6m 49s
NC In Julius Docker(DSP-HTTPS-BRIDGE)
1m 55s
NC In Host(Redis) Deploy options
2m 3s
Tests-Deploy-OK
4s
Annotations
6 warnings
|
NC In Host
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. 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/
|
|
NC In Host(network=host)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. 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/
|
|
NC In Host(Redis)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. 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/
|
|
NC In Host (HaRP-Host network)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. 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/
|
|
NC In Host(Redis) Deploy options
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. 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/
|
|
NC In Host (Manual HaRP-Host network)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. 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 | |
|---|---|---|---|
|
dsp_http_container.json
|
3.24 KB |
sha256:36dc6effc0ab07e36a7d7532eeaf4a55dcae0a456e4c4f546cb3e55833d0bcdb
|
|
|
dsp_http_container.log
|
945 Bytes |
sha256:eb7fdbd6b58f45656c6e00cb4a07c0f476907e375241b556f4cb55df4702b454
|
|
|
dsp_http_nextcloud.log
|
593 Bytes |
sha256:3d55cb1d2f33edb67c125892a9fa627dd637af7e26c88064ecb5c37de821d062
|
|
|
dsp_https_bridge_container.json
|
3.36 KB |
sha256:e0ee9b6e7d6caf2c86238f42ba07a3b270cc34473fff9b77b5c363a3030a5bc4
|
|
|
dsp_https_bridge_container.log
|
890 Bytes |
sha256:372f6f471161bce71a80960ce554e08d473d730667b5f268de844888bb5b7883
|
|
|
dsp_https_bridge_haproxy.log
|
3.71 KB |
sha256:e6371acb16b577d9e5f6712e78142df37798236236042317933a8f2cf3c2cf49
|
|
|
dsp_https_bridge_nextcloud.log
|
598 Bytes |
sha256:a15b38beada1170965229485a9854a616702f83159c481abfda3305c306de180
|
|
|
dsp_https_container.json
|
3.29 KB |
sha256:86dd69ffc50118b377c7c9ea03c1df6f0296bdafbd0f2d15ef928f64adafc475
|
|
|
dsp_https_container.log
|
885 Bytes |
sha256:3de47c882e3d502ef9bbb448485df0f8a5028037528472f80b9ed06ac3c7b034
|
|
|
dsp_https_haproxy.log
|
3.69 KB |
sha256:6d3d052708a8e584755ce3342d257036205814687ea23bdb404a8765240b8211
|
|
|
dsp_https_nextcloud.log
|
601 Bytes |
sha256:f5be68cc89a0ec049be0f7f97177a099c029fb4324d270399777a68da1bc787f
|
|
|
nc_docker_app_docker_container.json
|
147 Bytes |
sha256:44ea5bcb0ce29c7e73bd6eac4cf1cadcf107ce94b3ee21573acd90b946d2e039
|
|
|
nc_docker_app_docker_container.log
|
945 Bytes |
sha256:359f8a6d0f4e5d21c952c6e27b5185a248644fce4e71bbfa7885940e7085d2ed
|
|
|
nc_docker_app_docker_nextcloud.log
|
597 Bytes |
sha256:3814ed7acd5079d357c9dbbcc830d820b979ef5a672ed103019662a136aeebcf
|
|
|
nc_host_app_docker_container.json
|
3.22 KB |
sha256:5d50c1cb3bee1ed4f00f98079ac566cd830b47876358981a85933694c218a4ed
|
|
|
nc_host_app_docker_container.log
|
934 Bytes |
sha256:c5242d61360acf08978d770a042b6f628960ac0c6d5236de0101344fe2bd3644
|
|
|
nc_host_app_docker_nextcloud.log
|
55.5 KB |
sha256:9ef0a4699bc0c1a595118562a861e6028e9d2dcf0ea03fe81d6db8b7635e11b9
|
|
|
nc_host_app_docker_redis_container.json
|
3.22 KB |
sha256:1adcd93577a244f4292a1519998813c567bf639e3fd0b18549b53d01deba99a2
|
|
|
nc_host_app_docker_redis_container.log
|
946 Bytes |
sha256:35f6f174b4c656df5ac6ca6fc21a3349b97187ef69e1e49a9c3554fb66ec7a6d
|
|
|
nc_host_app_docker_redis_deploy_options_container.json
|
3.3 KB |
sha256:8ebfd91dfbb692f89c719f3d116d2c35b05d4c0dcd0182312214bc4856e3c48f
|
|
|
nc_host_app_docker_redis_deploy_options_container.log
|
930 Bytes |
sha256:491168694aaf27eee6c1ead7c3f6be9a921f93fe74418d1b1b2de779ff99405e
|
|
|
nc_host_app_docker_redis_deploy_options_nextcloud.log
|
62 KB |
sha256:66f51fe39cdea7f1a832fd6038c5d2db6578e2262d7fe31aecd2ec1e5d733d87
|
|
|
nc_host_app_docker_redis_nextcloud.log
|
55.4 KB |
sha256:6fe001719c4c068de709343329cb83462045287a41c3ecaf6ec8fed61da74a7e
|
|
|
nc_host_network_host_container.json
|
3.2 KB |
sha256:ab1c0930de7390e3c854e46686f7c63dd2bb351acdaed434a64171dbaf13029d
|
|
|
nc_host_network_host_container.log
|
940 Bytes |
sha256:003f9cfa5972f7440cf86c93ff69681a55f9bdd15472e0e9f63342b6b7dcb855
|
|
|
nc_host_network_host_nextcloud.log
|
55.3 KB |
sha256:0fbd04f98f5cd275c96830661adf2a1105e754fdd71159a264ab5ef998970540
|
|