chore(deps): update node.js to v22 · bicstone/backlog-notify@13c3c28

Triggered via pull request November 5, 2024 03:34

synchronize #227

renovate/node-22.x

Status Success

Total duration 50s

Artifacts –

test.yml

on: pull_request

2 errors and 10 warnings

Error: Test Error

Error: Test Error

Build and Test: src/common/stdout.spec.ts#L15

'process.stdout' will use Object's default stringification format ('[object Object]') when stringified

Build and Test: src/common/stdout.spec.ts#L17

'process.stdout' will use Object's default stringification format ('[object Object]') when stringified

Build and Test: src/main.ts#L33

Unexpected object value in conditional. The condition is always true

Build and Test: src/main.ts#L33

Unnecessary conditional, value is always truthy

Build and Test: src/main.ts#L48

Unexpected object value in conditional. The condition is always true

Build and Test: src/main.ts#L48

Unnecessary conditional, value is always truthy

Build and Test: src/main/getConfigs.ts#L133

Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly

Build and Test: src/main/getConfigs.ts#L133

Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator

Build and Test: src/main/getConfigs.ts#L133

Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly

Build and Test: src/main/getConfigs.ts#L133

Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator