Skip to content
On PR code update

chore(deps): bump actions/setup-node from 4.0.4 to 4.1.0 #3675

Sign in to view logs

chore(deps): bump actions/setup-node from 4.0.4 to 4.1.0

chore(deps): bump actions/setup-node from 4.0.4 to 4.1.0 #3675

Triggered via pull request November 4, 2024 11:01
@dependabotdependabot[bot]
synchronize #3258
dependabot/github_actions/actions/setup-node-4.1.0
Status Success
Total duration 1m 41s
Artifacts –

pr-run-linting-check-and-unit-tests.yml

on: pull_request
run-unit-tests  /  check-layer-publisher
1m 23s
run-unit-tests / check-layer-publisher
run-unit-tests  /  check-docs-snippets
46s
run-unit-tests / check-docs-snippets
run-unit-tests  /  check-docs
45s
run-unit-tests / check-docs
Matrix: run-unit-tests / check-examples
Matrix: run-unit-tests / code-quality
Matrix: run-unit-tests / run-linting-check-and-unit-tests-on-utilities
Fit to window
Zoom out
Zoom in

Annotations

36 errors
run-unit-tests / check-docs-snippets
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-docs-snippets
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-docs
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-docs
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/logger)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-examples (app)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-examples (app)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/commons)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (20, packages/idempotency)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/batch)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/event-handler)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / code-quality (18, packages/jmespath)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-layer-publisher
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / check-layer-publisher
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-unit-tests / run-linting-check-and-unit-tests-on-utilities (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.