Skip to content

admin: require path segment boundary in remote access control (#7673) #7803

admin: require path segment boundary in remote access control (#7673)

admin: require path segment boundary in remote access control (#7673) #7803

Triggered via push April 27, 2026 14:43
Status Success
Total duration 5m 36s
Artifacts 3

ci.yml

on: push
test (s390x on IBM Z)
test (s390x on IBM Z)
goreleaser-check
goreleaser-check
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
test (mac, 1.26)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
test (linux, 1.26)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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/
test (windows, 1.26)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. 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
caddy_Linux_go1.26_2d33271
46.3 MB
sha256:e73cf8d4a61f3e2276b00c326750425dfde3ea13e4752dcd697c4fb4dbf96665
caddy_Windows_go1.26_2d33271
47.2 MB
sha256:a9b2c8651da0a8230a7617c7597940b46fa2b15f175c2c4f320e102e5f8aed42
caddy_macOS_go1.26_2d33271
44.6 MB
sha256:156ef9894f420cfce2725b35315ecb4eea1add8863b15d87e88d14a6fae5990b