Skip to content
pr-check

chore(deps-dev): bump the eslint group across 1 directory with 4 updates #3658

Sign in to view logs

chore(deps-dev): bump the eslint group across 1 directory with 4 updates

chore(deps-dev): bump the eslint group across 1 directory with 4 updates #3658

Triggered via pull request April 3, 2026 02:27
@dependabotdependabot[bot]
synchronize #2415
dependabot/npm_and_yarn/eslint-1b8ab2062e
Status Failure
Total duration 17m 30s
Artifacts 1

pr-check.yaml

on: pull_request
e2e tests
17m 27s
e2e tests
Matrix: lint-format-unit
Fit to window
Zoom out
Zoom in

Annotations

30 errors and 1 warning
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L324
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L285
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L247
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L158
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L90
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L66
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/container-utils.ts#L55
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/api-impl.ts#L378
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/api-impl.ts#L320
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / ubuntu-22.04: packages/backend/src/api-impl.ts#L305
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L324
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L285
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L247
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L158
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L90
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L66
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/container-utils.ts#L55
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/api-impl.ts#L378
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/api-impl.ts#L320
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / macos-14: packages/backend/src/api-impl.ts#L305
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L324
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L285
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L247
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L158
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L90
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L66
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/container-utils.ts#L55
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/api-impl.ts#L378
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/api-impl.ts#L320
There is no `cause` attached to the symptom error being thrown
linter, formatter, and tests / windows-2022: packages/backend/src/api-impl.ts#L305
There is no `cause` attached to the symptom error being thrown
e2e tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-actions/buildah-build@v2. 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/

Artifacts

Produced during runtime
Name Size Digest
e2e-tests
85.1 MB
sha256:f15801381103578b241300bb8cb6531c5c654fb657af49816df53a64f8449ac6