feat: add kebab-case id field to project schema #37
alessiomaurotest.yml
on: pull_request
Matrix: Python Tests
Matrix: TypeScript Tests
Build Check
0s
Annotations
14 errors and 6 warnings
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should exclude symlinks from local components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:269:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should have correct sourcePath format for local components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:257:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should have correct sourcePath format for shared components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:245:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should include required fields for local components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:226:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should include required fields for shared components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:206:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should output JSON with --format json:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:194:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get (basic) > should display project tree:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:184:22
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get --download > should use project name as default output:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:171:7
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get --download > should copy local components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:148:7
|
|
tests/cli-commands.test.ts > CLI Commands > cldpm get --download > should download project with shared components:
typescript/tests/cli-commands.test.ts#L113
Error: CLI failed: ✗ Failed to get project: [
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"id"
],
"message": "Required"
}
]
❯ runCli tests/cli-commands.test.ts:113:13
❯ tests/cli-commands.test.ts:124:7
|
|
TypeScript Tests (20)
The strategy configuration was canceled because "test-typescript._22" failed
|
|
TypeScript Tests (20)
The operation was canceled.
|
|
TypeScript Tests (18)
The strategy configuration was canceled because "test-typescript._22" failed
|
|
TypeScript Tests (18)
The operation was canceled.
|
|
Python 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. 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 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/
|
|
Python 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/
|
|
TypeScript Tests (22)
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 Tests (20)
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 Tests (18)
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/
|