CI: [pull] develop from baserow:develop #376
pull[bot]ci.yml
on: pull_request
Check build and publish
2s
Detect Changed Files
11s
Build Backend CI Image
27s
Build Web-Frontend CI Image
4m 20s
Dockerfile Lint (hadolint)
0s
Helm Chart Lint
0s
Zapier Integration Tests
0s
Check MJML Email Templates Compiled
0s
Matrix: test-e2e
Matrix: test-frontend
Matrix: test-backend
Publish develop-latest web-frontend image
Publish develop-latest backend image
0s
CI Status
2s
Publish develop-latest all-in-one image
Trigger SaaS GitLab Pipeline
Publish develop-latest Cloudron image
0s
Annotations
2 errors and 3 warnings
|
Build Backend CI Image
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/code/app-python-baserow/backend_dev:ci-5f6249346074b0e71eb741bc70e61120cae714c1: denied: installation not allowed to Write organization package
|
|
Build Web-Frontend CI Image
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/code/app-python-baserow/web-frontend_dev:ci-5f6249346074b0e71eb741bc70e61120cae714c1: denied: installation not allowed to Write organization package
|
|
Detect Changed Files
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. 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 Backend CI Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-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 Web-Frontend CI Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-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/
|