Add package-lock.json and update .gitignore to allow it #4
ci.yml
on: push
Python: memorylayer-server
24s
Python: memorylayer-client
18s
Matrix: test-typescript
Annotations
10 errors and 4 warnings
|
TypeScript: memorylayer-mcp-server
Process completed with exit code 2.
|
|
TypeScript: memorylayer-mcp-server
Cannot find module '@scitrera/memorylayer-sdk' or its corresponding type declarations.
|
|
TypeScript: memorylayer-mcp-server
Cannot find module '@scitrera/memorylayer-sdk' or its corresponding type declarations.
|
|
TypeScript: memorylayer-mcp-server
Cannot find module '@scitrera/memorylayer-sdk' or its corresponding type declarations.
|
|
TypeScript: memorylayer-mcp-server
Cannot find module '@scitrera/memorylayer-sdk' or its corresponding type declarations.
|
|
TypeScript: memorylayer-mcp-server
Parameter 'memory' implicitly has an 'any' type.
|
|
TypeScript: memorylayer-mcp-server
Cannot find module '@scitrera/memorylayer-sdk' or its corresponding type declarations.
|
|
TypeScript: memorylayer-mcp-server
Cannot find module '@scitrera/memorylayer-sdk' or its corresponding type declarations.
|
|
Python: memorylayer-client
Process completed with exit code 1.
|
|
Python: memorylayer-server
Process completed with exit code 1.
|
|
TypeScript: memorylayer-sdk
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-node@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/
|
|
TypeScript: memorylayer-mcp-server
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-node@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/
|
|
Python: memorylayer-client
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/
|
|
Python: memorylayer-server
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/
|