Skip to content

Document an example content structure. (#30) #167

Document an example content structure. (#30)

Document an example content structure. (#30) #167

Triggered via push May 6, 2026 13:40
Status Success
Total duration 43m 34s
Artifacts 1

main.yml

on: push
config  /  config
7s
config / config
Matrix: backend / Backend: Test
Waiting for pending jobs
backend  /  ...  /  lint
backend / Backend: Lint / lint
frontend  /  ...  /  Code analysis check
1m 17s
frontend / Frontend: Codeanalysis / Code analysis check
frontend  /  ...  /  i18n checks
2m 5s
frontend / Frontend: i18n / i18n checks
frontend  /  ...  /  Unit tests
1m 20s
frontend / Frontend: Unit tests / Unit tests
docs  /  ...  /  Documentation
docs / Docs: Build / Documentation
backend  /  ...  /  Test coverage with Pytest
backend / Backend: Coverage / Test coverage with Pytest
frontend  /  ...  /  Image ghcr.io/collective/tech-event-frontend:sha-b058a16
4m 53s
frontend / Frontend: Build and publish container image / Image ghcr.io/collective/tech-event-frontend:sha-b058a16
backend  /  ...  /  build
backend / Backend: Build and publish Container Image / build
backend  /  Final report
backend / Final report
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
config / config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3.0.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/
frontend / Frontend: Codeanalysis / Code analysis check
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/setup-node@v4, astral-sh/setup-uv@v5. 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/
frontend / Frontend: Unit tests / Unit tests
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/setup-node@v4, astral-sh/setup-uv@v5. 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/
frontend / Frontend: i18n / i18n checks
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/setup-node@v4, astral-sh/setup-uv@v5. 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/
Default value for global ARG results in an empty or invalid base image name: frontend/Dockerfile#L21
InvalidDefaultArgInFrom: Default value for ARG plone/frontend-prod-config:${VOLTO_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: frontend/Dockerfile#L3
InvalidDefaultArgInFrom: Default value for ARG plone/frontend-builder:${VOLTO_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/

Artifacts

Produced during runtime
Name Size Digest
collective~tech-event~F8TSQF.dockerbuild Expired
77.9 KB
sha256:0d58b66ee16f2351a9a8a2a102817a8de96d92d94df0beaf9318cd5a53d6eafa