Skip to content

build(deps): Bump super-linter/super-linter from slim-v8.0.0 to slim-v8.6.0 in the docker-dependencies group across 1 directory #543

build(deps): Bump super-linter/super-linter from slim-v8.0.0 to slim-v8.6.0 in the docker-dependencies group across 1 directory

build(deps): Bump super-linter/super-linter from slim-v8.0.0 to slim-v8.6.0 in the docker-dependencies group across 1 directory #543

Triggered via pull request March 20, 2026 04:06
Status Success
Total duration 6m 46s
Artifacts 1

__pull-request-ci.yml

on: pull_request
Matrix: ci / linter / 🛡️ CodeQL Analysis
ci  /  ...  /  🧹 Lint Code Base
1m 15s
ci / linter / 🧹 Lint Code Base
ci  /  ...  /  prepare-actions-linting
8s
ci / linter / prepare-actions-linting
ci  /  ...  /  📌 Check GitHub Actions Pinning
7s
ci / linter / 📌 Check GitHub Actions Pinning
ci  /  ...  /  Tests for "check/url-lighthouse" action
35s
ci / test-action-check-url-lighthouse / Tests for "check/url-lighthouse" action
ci  /  ...  /  Tests for "check/url-ping" action
27s
ci / test-action-check-url-ping / Tests for "check/url-ping" action
ci  /  ...  /  Tests for "deploy/jekyll" and "deploy/jampack" actions
1m 36s
ci / test-action-deploy-jekyll / Tests for "deploy/jekyll" and "deploy/jampack" actions
ci  /  ...  /  Tests for "deployment" actions
13s
ci / test-action-deployment / Tests for "deployment" actions
Matrix: ci / test-action-deploy-argocd-manifest-files / tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 8 warnings
ci / test-action-check-url-ping / Tests for "check/url-ping" action
URL check failed after 2 attempt(s) within 5 seconds. Last error: Unexpected status code: 500. Expected one of: 200
ci / test-action-check-url-ping / Tests for "check/url-ping" action
Invalid URL [code=ERR_INVALID_URL]
ci / test-action-check-url-ping / Tests for "check/url-ping" action
URL check failed after 1 attempt(s) within 1 seconds. Last error: Request to http://localhost:1080/very-slow timed out after 0.80 seconds (attempt budget)
ci / linter / 🛡️ CodeQL Analysis (actions)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
ci / test-action-check-url-ping / Tests for "check/url-ping" action
Attempt 2/2 failed: Unexpected status code: 500. Expected one of: 200
ci / test-action-check-url-ping / Tests for "check/url-ping" action
Attempt 1/2 failed: Unexpected status code: 500. Expected one of: 200
ci / test-action-check-url-ping / Tests for "check/url-ping" action
Attempt 2/3 failed: Unexpected status code: 500. Expected one of: 200
ci / test-action-check-url-ping / Tests for "check/url-ping" action
Attempt 1/3 failed: Unexpected status code: 500. Expected one of: 200
ci / test-action-check-url-ping / Tests for "check/url-ping" action
Attempt 1/1 failed: Request to http://localhost:1080/very-slow timed out after 0.80 seconds (attempt budget)
ci / test-action-deployment / Tests for "deployment" actions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-github-app-token@29824e69f54612133e76f7eaac726eef6c875baf. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
ci / test-action-deploy-jekyll / Tests for "deploy/jekyll" and "deploy/jampack" actions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
23328610158-543-lighthouse-results-1773979838489-4266246a-db7c-4bb9-8a35-4bde96d2c1d0
768 KB
sha256:8434a1758ff64d718f393213cccb72cb50cd5b4b668068846c1a62fdc9f590df