Merge pull request #4805 from bcgov/4747-add-valid-to-and-valid-from-… #17088
main.yaml
on: push
check-nx-affected
36s
build-backend
/
docker-build
1m 41s
build-dashboard-e2e
/
docker-build
1m 44s
build-administration
/
docker-build
1m 48s
check-backend-changes
/
check
6s
build-compliance
/
docker-build
2m 4s
build-registration
/
docker-build
1m 40s
build-reporting
/
docker-build
1m 44s
check-frontend-changes
/
check
6s
build-dashboard
/
docker-build
1m 41s
trivy
/
analyze
28s
Matrix: codeql / analyze
test-administration-e2e
/
🧪 e2e tests chromium
8m 15s
test-administration-e2e
/
happo-skip-not-affected
0s
test-backend
/
pythontests
8m 23s
test-compliance-e2e
/
🧪 e2e tests chromium
10m 27s
test-compliance-e2e
/
happo-skip-not-affected
0s
test-registration-e2e
/
🧪 e2e tests chromium
5m 28s
test-registration-e2e
/
happo-skip-not-affected
0s
test-reporting-e2e
/
🧪 e2e tests chromium
9m 36s
test-reporting-e2e
/
happo-skip-not-affected
0s
test-dashboard-e2e
/
🧪 e2e tests chromium
6m 8s
test-dashboard-e2e
/
happo-skip-not-affected
0s
test-code
/
nx-tests
35s
test-code
/
yarn-audit
43s
test-code
/
prek
2m 53s
test-code
/
check-migrations
1m 5s
test-code
/
check-immutable-migrations
1m 3s
test-code
/
check-test-data
2m 59s
test-code
/
check-dev-data
3m 13s
Annotations
14 warnings
|
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-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 / 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-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 / 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-registration-e2e / 🧪 e2e tests chromium
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-dashboard-e2e / 🧪 e2e tests chromium
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/
|
|
test-administration-e2e / 🧪 e2e tests chromium
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-reporting-e2e / 🧪 e2e tests chromium
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-compliance-e2e / 🧪 e2e tests chromium
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~82NN1H.dockerbuild
|
78.3 KB |
sha256:507559e6d75b05d98128bef0e3e29684b2fd1bdd7aba4347059a466e61e58cf3
|
|
|
trivy-results
|
12.1 KB |
sha256:1fd924b0663c54133ca6212490039d82bc34a37175b417cef96f271b12c34ae9
|
|