⚡ Bolt: Replace lambda with operator.itemgetter for event sorting (#144) #272
Annotations
11 errors and 6 warnings
|
Code Quality
Process completed with exit code 1.
|
|
ruff (F401):
src/ledgermind/core/api/memory.py#L5
src/ledgermind/core/api/memory.py:5:8: F401 `shutil` imported but unused
help: Remove unused import: `shutil`
|
|
ruff (F401):
src/ledgermind/core/api/memory.py#L3
src/ledgermind/core/api/memory.py:3:8: F401 `json` imported but unused
help: Remove unused import: `json`
|
|
ruff (F401):
src/ledgermind/core/api/memory.py#L2
src/ledgermind/core/api/memory.py:2:8: F401 `yaml` imported but unused
help: Remove unused import: `yaml`
|
|
ruff (E701):
src/ledgermind/core/api/bridge.py#L223
src/ledgermind/core/api/bridge.py:223:24: E701 Multiple statements on one line (colon)
|
|
ruff (E701):
src/ledgermind/core/api/bridge.py#L120
src/ledgermind/core/api/bridge.py:120:24: E701 Multiple statements on one line (colon)
|
|
ruff (E701):
src/ledgermind/core/api/bridge.py#L57
src/ledgermind/core/api/bridge.py:57:34: E701 Multiple statements on one line (colon)
|
|
ruff (F401):
src/ledgermind/core/api/bridge.py#L5
src/ledgermind/core/api/bridge.py:5:8: F401 `time` imported but unused
help: Remove unused import: `time`
|
|
ruff (F401):
src/ledgermind/core/api/bridge.py#L2
src/ledgermind/core/api/bridge.py:2:8: F401 `re` imported but unused
help: Remove unused import: `re`
|
|
ruff (F401):
src/ledgermind/core/api/base_service.py#L1
src/ledgermind/core/api/base_service.py:1:20: F401 `typing.Any` imported but unused
help: Remove unused import: `typing.Any`
|
|
ruff (F401):
src/ledgermind/core/api/__init__.py#L1
src/ledgermind/core/api/__init__.py:1:21: F401 `.memory.Memory` imported but unused; consider removing, adding to `__all__`, or using a redundant alias
help: Use an explicit re-export: `Memory as Memory`
|
|
Security Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/
|
|
Code Quality
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
Tests (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
Tests (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
Build Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
|
|
Tests (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, codecov/codecov-action@v4. 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 | |
|---|---|---|---|
|
security-reports
|
10.4 KB |
sha256:5163fea6ae81d9ba4bea9bd5eaf35fc0e38bbd089604db686fc39e30d14970ba
|
|