Skip to content
CI

Support nested files and folders for Skills #9899

Sign in to view logs

Support nested files and folders for Skills

Support nested files and folders for Skills #9899

Triggered via pull request March 22, 2026 21:29
@dimaMachinadimaMachina
synchronize #2719
prd-6236
Status Failure
Total duration 7m 12s
Artifacts 1

ci.yml

on: pull_request
ci
3m 53s
ci
Create Agents E2E Tests
7m 7s
Create Agents E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 2 warnings
ci
Process completed with exit code 1.
ci
@inkeep/agents-sdk#test: command (/home/runner/work/agents/agents/packages/agents-sdk) /home/runner/setup-pnpm/node_modules/.bin/pnpm run test exited (1)
src/__tests__/skill-loader.test.ts > skill-loader > metadata > accepts with string values: packages/agents-sdk/src/skill-loader.ts#L38
Error: ✖ Too small: expected string to have >=1 characters → at content ❯ src/skill-loader.ts:38:13 ❯ loadSkills src/skill-loader.ts:32:16 ❯ src/__tests__/skill-loader.test.ts:217:23
src/__tests__/skill-loader.test.ts > skill-loader > name > rejects value that do not match the directory: packages/agents-sdk/src/__tests__/skill-loader.test.ts#L150
AssertionError: expected [Function] to throw error including 'Skill name "y" does not match directo…' but got '✖ Too small: expected string to have …' - Expected + Received - Skill name "y" does not match directory "x" + ✖ Too small: expected string to have >=1 characters + → at content ❯ src/__tests__/skill-loader.test.ts:150:38
src/__tests__/skill-loader.test.ts > skill-loader > loads a skill with required fields: packages/agents-sdk/src/skill-loader.ts#L38
Error: ✖ Too small: expected string to have >=1 characters → at content ❯ src/skill-loader.ts:38:13 ❯ loadSkills src/skill-loader.ts:32:16 ❯ src/__tests__/skill-loader.test.ts:44:21
src/__tests__/project.test.ts > Project > toFullProjectDefinition > should include nested skill files in the full project definition: packages/agents-sdk/src/__tests__/project.test.ts#L584
AssertionError: expected { files: [ { …(2) }, { …(2) } ] } to match object { …(2) } - Expected + Received @@ -13,7 +13,6 @@ { "content": "Check weather alerts", "filePath": "reference/safety-checklist.txt", }, ], - "id": "weather-safety-guardrails", } ❯ src/__tests__/project.test.ts:584:68
Create Agents E2E Tests
Process completed with exit code 1.
src/__tests__/manage/integration/skills.test.ts > Skill Routes > should remove all skill files when SKILL.md is removed from the file set: agents-api/src/__tests__/manage/integration/skills.test.ts#L177
AssertionError: expected 400 to be 200 // Object.is equality - Expected + Received - 200 + 400 ❯ src/__tests__/manage/integration/skills.test.ts:177:35
ci
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, pnpm/action-setup@c5ba7f7862a0f64c1b1a05fbac13e0b8e86ba08c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Create Agents E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@c5ba7f7862a0f64c1b1a05fbac13e0b8e86ba08c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
vitest-screenshots Expired
106 KB
sha256:c7d552c243b1f3b519937f92d4b9c2ba27ee756b1a2fe6419df32ee4eab4f2dc