Skip to content

chore(deps): bump launch-editor from 2.13.2 to 2.14.1 in /bciers #17087

chore(deps): bump launch-editor from 2.13.2 to 2.14.1 in /bciers

chore(deps): bump launch-editor from 2.13.2 to 2.14.1 in /bciers #17087

Triggered via pull request June 16, 2026 19:08
Status Failure
Total duration 12m 13s
Artifacts 2

main.yaml

on: pull_request
check-nx-affected
1m 8s
check-nx-affected
build-backend  /  docker-build
34s
build-backend / docker-build
build-dashboard-e2e  /  docker-build
1m 55s
build-dashboard-e2e / docker-build
build-administration  /  docker-build
2m 14s
build-administration / docker-build
check-backend-changes  /  check
7s
check-backend-changes / check
build-compliance  /  docker-build
1m 57s
build-compliance / docker-build
build-registration  /  docker-build
1m 51s
build-registration / docker-build
build-reporting  /  docker-build
2m 15s
build-reporting / docker-build
check-frontend-changes  /  check
15s
check-frontend-changes / check
build-dashboard  /  docker-build
1m 48s
build-dashboard / docker-build
trivy  /  analyze
28s
trivy / analyze
Matrix: codeql / analyze
test-administration-e2e  /  happo-skip-not-affected
test-administration-e2e / happo-skip-not-affected
test-administration-e2e  /  🧪 e2e tests chromium
test-administration-e2e / 🧪 e2e tests chromium
test-backend  /  pythontests
8m 50s
test-backend / pythontests
test-compliance-e2e  /  happo-skip-not-affected
test-compliance-e2e / happo-skip-not-affected
test-compliance-e2e  /  🧪 e2e tests chromium
test-compliance-e2e / 🧪 e2e tests chromium
test-registration-e2e  /  happo-skip-not-affected
test-registration-e2e / happo-skip-not-affected
test-registration-e2e  /  🧪 e2e tests chromium
test-registration-e2e / 🧪 e2e tests chromium
test-dashboard-e2e  /  happo-skip-not-affected
test-dashboard-e2e / happo-skip-not-affected
test-dashboard-e2e  /  🧪 e2e tests chromium
test-dashboard-e2e / 🧪 e2e tests chromium
test-reporting-e2e  /  happo-skip-not-affected
test-reporting-e2e / happo-skip-not-affected
test-reporting-e2e  /  🧪 e2e tests chromium
test-reporting-e2e / 🧪 e2e tests chromium
test-code  /  nx-tests
10m 44s
test-code / nx-tests
test-code  /  yarn-audit
55s
test-code / yarn-audit
test-code  /  prek
3m 20s
test-code / prek
test-code  /  check-migrations
1m 16s
test-code / check-migrations
test-code  /  check-immutable-migrations
59s
test-code / check-immutable-migrations
test-code  /  check-test-data
3m 11s
test-code / check-test-data
test-code  /  check-dev-data
3m 27s
test-code / check-dev-data
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 8 warnings
build-backend / docker-build
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/bcgov/cas-reg-backend:pr-4807: denied: installation not allowed to Write organization package
build-dashboard / docker-build
Process completed with exit code 1.
build-dashboard-e2e / docker-build
Process completed with exit code 1.
build-compliance / docker-build
Process completed with exit code 1.
build-registration / docker-build
Process completed with exit code 1.
build-administration / docker-build
Process completed with exit code 1.
build-reporting / docker-build
Process completed with exit code 1.
test-backend / pythontests
Process completed with exit code 2.
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']
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 / 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-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-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~1AEJD7.dockerbuild
72 KB
sha256:1fa73cee7a72e8610621ec47458e22205e8dc4b9125bb347e5bb67590cf380b3
trivy-results
12.1 KB
sha256:fffbe4925ca48c1d0c093efcee0d852a713cf9e6e9c579d60967f4f0ef44e59f