Update regulated product valid date for lime recovered by kiln #17079
main.yaml
on: pull_request
check-nx-affected
58s
build-backend
/
docker-build
2m 2s
build-dashboard-e2e
/
docker-build
2m 4s
check-backend-changes
/
check
9s
build-administration
/
docker-build
2m 20s
build-compliance
/
docker-build
2m 14s
build-registration
/
docker-build
1m 58s
build-reporting
/
docker-build
2m 7s
check-frontend-changes
/
check
9s
build-dashboard
/
docker-build
2m 0s
trivy
/
analyze
30s
Matrix: codeql / analyze
test-backend
/
pythontests
8m 15s
test-administration-e2e
/
🧪 e2e tests chromium
0s
test-administration-e2e
/
happo-skip-not-affected
1m 33s
test-compliance-e2e
/
🧪 e2e tests chromium
0s
test-compliance-e2e
/
happo-skip-not-affected
1m 35s
test-registration-e2e
/
🧪 e2e tests chromium
test-registration-e2e
/
happo-skip-not-affected
1m 29s
test-dashboard-e2e
/
🧪 e2e tests chromium
0s
test-dashboard-e2e
/
happo-skip-not-affected
1m 29s
test-reporting-e2e
/
🧪 e2e tests chromium
0s
test-reporting-e2e
/
happo-skip-not-affected
1m 47s
test-code
/
nx-tests
59s
test-code
/
yarn-audit
49s
test-code
/
prek
3m 17s
test-code
/
check-migrations
1m 0s
test-code
/
check-immutable-migrations
58s
test-code
/
check-test-data
3m 6s
test-code
/
check-dev-data
3m 18s
Annotations
9 warnings
|
test-code / check-migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 / docker-build
Unexpected input(s) 'install', valid inputs are ['version', 'driver', 'driver-opts', 'buildkitd-flags', 'buildkitd-config', 'buildkitd-config-inline', 'use', 'name', 'endpoint', 'platforms', 'append', 'keep-state', 'cache-binary', 'cleanup']
|
|
Default value for global ARG results in an empty or invalid base image name:
bc_obps/Dockerfile#L7
InvalidDefaultArgInFrom: Default value for ARG dhi.io/python:${PYTHON_VERSION}-debian13-dev results in empty or invalid base image name
More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
|
|
build-backend / docker-build
Unexpected input(s) 'install', valid inputs are ['version', 'driver', 'driver-opts', 'buildkitd-flags', 'buildkitd-config', 'buildkitd-config-inline', 'use', 'name', 'endpoint', 'platforms', 'append', 'keep-state', 'cache-binary', 'cleanup']
|
|
test-code / check-immutable-migrations
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-code / check-test-data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-code / prek
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-code / check-dev-data
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-backend / pythontests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Gr1N/setup-poetry@v9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 | |
|---|---|---|---|
|
bcgov~cas-registration~K3IKKE.dockerbuild
|
82.3 KB |
sha256:1e129e824858175b3e26c1cfd760bb3b04f3578beb9234e47cf0631c4e373fb9
|
|
|
trivy-results
|
12.1 KB |
sha256:f95a40fd2067521cb2e7f0f4ca51325289bd806f6e75922e4e6eae20a28ab5ef
|
|