Skip to content

database: use explicit scope for read/update to avoid linting issues #1805

database: use explicit scope for read/update to avoid linting issues

database: use explicit scope for read/update to avoid linting issues #1805

Triggered via push February 21, 2024 08:29
Status Cancelled
Total duration 15m 4s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
Build/Test [Ubuntu]
Process completed with exit code 2.
Code linting
The operation was canceled.
Code formatting
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build/Test [Ubuntu]
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Code linting
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.