Skip to content

release: bump version to 3.1.1 #4

release: bump version to 3.1.1

release: bump version to 3.1.1 #4

Triggered via push June 23, 2026 14:27
Status Failure
Total duration 51s
Artifacts

ci.yml

on: push
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

27 errors and 3 warnings
build-and-test (bun, 1.3)
Process completed with exit code 1.
src/__tests__/manager-tools.test.ts > delegate_task tool > adds specialist from catalog if not in team (catalog fallback): src/__tests__/manager-tools.test.ts#L277
AssertionError: expected 'Error: Specialist "software-developme…' to have property "title" ❯ src/__tests__/manager-tools.test.ts:277:20
src/__tests__/manager-tools.test.ts > propose_team tool > proposes valid specialists in PLANNING phase: src/__tests__/manager-tools.test.ts#L110
AssertionError: expected 'Error: Invalid specialist IDs not fou…' to have property "title" with value 'Team Proposal — Awaiting Human Approv…' - Expected: "Team Proposal — Awaiting Human Approval" + Received: undefined ❯ src/__tests__/manager-tools.test.ts:110:20
src/__tests__/catalog.test.ts > catalog loader > software-development division has multiple personas: src/__tests__/catalog.test.ts#L97
AssertionError: expected 0 to be greater than 5 ❯ src/__tests__/catalog.test.ts:97:25
src/__tests__/catalog.test.ts > catalog loader > loads all personas from embedded catalog: src/__tests__/catalog.test.ts#L70
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog.test.ts:70:29
src/__tests__/catalog-tools.test.ts > get_specialist tool > returns full specialist details for valid ID: src/__tests__/catalog-tools.test.ts#L84
AssertionError: expected 'Error: Specialist not found: software…' to have property "title" ❯ src/__tests__/catalog-tools.test.ts:84:20
src/__tests__/catalog-tools.test.ts > list_specialists tool > filters by search term: src/__tests__/catalog-tools.test.ts#L49
AssertionError: expected '[Mesa · Phase: catalog]\n\nShowing 0-…' to contain 'backend' - Expected + Received - backend + [Mesa · Phase: catalog] + + Showing 0-0 of 0 specialists in division all + + | Emoji | Name | ID | Division | + |-------|------|----|----------| ❯ src/__tests__/catalog-tools.test.ts:49:20
src/__tests__/catalog-tools.test.ts > list_specialists tool > filters by division: src/__tests__/catalog-tools.test.ts#L39
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog-tools.test.ts:39:28
src/__tests__/catalog-tools.test.ts > list_specialists tool > returns formatted output with all specialists: src/__tests__/catalog-tools.test.ts#L28
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog-tools.test.ts:28:28
build-and-test (node, 22)
Process completed with exit code 1.
src/__tests__/manager-tools.test.ts > delegate_task tool > adds specialist from catalog if not in team (catalog fallback): src/__tests__/manager-tools.test.ts#L277
AssertionError: expected 'Error: Specialist "software-developme…' to have property "title" ❯ src/__tests__/manager-tools.test.ts:277:20
src/__tests__/manager-tools.test.ts > propose_team tool > proposes valid specialists in PLANNING phase: src/__tests__/manager-tools.test.ts#L110
AssertionError: expected 'Error: Invalid specialist IDs not fou…' to have property "title" with value 'Team Proposal — Awaiting Human Approv…' - Expected: "Team Proposal — Awaiting Human Approval" + Received: undefined ❯ src/__tests__/manager-tools.test.ts:110:20
src/__tests__/catalog.test.ts > catalog loader > software-development division has multiple personas: src/__tests__/catalog.test.ts#L97
AssertionError: expected 0 to be greater than 5 ❯ src/__tests__/catalog.test.ts:97:25
src/__tests__/catalog.test.ts > catalog loader > loads all personas from embedded catalog: src/__tests__/catalog.test.ts#L70
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog.test.ts:70:29
src/__tests__/catalog-tools.test.ts > get_specialist tool > returns full specialist details for valid ID: src/__tests__/catalog-tools.test.ts#L84
AssertionError: expected 'Error: Specialist not found: software…' to have property "title" ❯ src/__tests__/catalog-tools.test.ts:84:20
src/__tests__/catalog-tools.test.ts > list_specialists tool > filters by search term: src/__tests__/catalog-tools.test.ts#L49
AssertionError: expected '[Mesa · Phase: catalog]\n\nShowing 0-…' to contain 'backend' - Expected + Received - backend + [Mesa · Phase: catalog] + + Showing 0-0 of 0 specialists in division all + + | Emoji | Name | ID | Division | + |-------|------|----|----------| ❯ src/__tests__/catalog-tools.test.ts:49:20
src/__tests__/catalog-tools.test.ts > list_specialists tool > filters by division: src/__tests__/catalog-tools.test.ts#L39
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog-tools.test.ts:39:28
src/__tests__/catalog-tools.test.ts > list_specialists tool > returns formatted output with all specialists: src/__tests__/catalog-tools.test.ts#L28
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog-tools.test.ts:28:28
build-and-test (node, 26)
Process completed with exit code 1.
src/__tests__/manager-tools.test.ts > delegate_task tool > adds specialist from catalog if not in team (catalog fallback): src/__tests__/manager-tools.test.ts#L277
AssertionError: expected 'Error: Specialist "software-developme…' to have property "title" ❯ src/__tests__/manager-tools.test.ts:277:20
src/__tests__/manager-tools.test.ts > propose_team tool > proposes valid specialists in PLANNING phase: src/__tests__/manager-tools.test.ts#L110
AssertionError: expected 'Error: Invalid specialist IDs not fou…' to have property "title" with value 'Team Proposal — Awaiting Human Approv…' - Expected: "Team Proposal — Awaiting Human Approval" + Received: undefined ❯ src/__tests__/manager-tools.test.ts:110:20
src/__tests__/catalog.test.ts > catalog loader > software-development division has multiple personas: src/__tests__/catalog.test.ts#L97
AssertionError: expected 0 to be greater than 5 ❯ src/__tests__/catalog.test.ts:97:25
src/__tests__/catalog.test.ts > catalog loader > loads all personas from embedded catalog: src/__tests__/catalog.test.ts#L70
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog.test.ts:70:29
src/__tests__/catalog-tools.test.ts > get_specialist tool > returns full specialist details for valid ID: src/__tests__/catalog-tools.test.ts#L84
AssertionError: expected 'Error: Specialist not found: software…' to have property "title" ❯ src/__tests__/catalog-tools.test.ts:84:20
src/__tests__/catalog-tools.test.ts > list_specialists tool > filters by search term: src/__tests__/catalog-tools.test.ts#L49
AssertionError: expected '[Mesa · Phase: catalog]\n\nShowing 0-…' to contain 'backend' - Expected + Received - backend + [Mesa · Phase: catalog] + + Showing 0-0 of 0 specialists in division all + + | Emoji | Name | ID | Division | + |-------|------|----|----------| ❯ src/__tests__/catalog-tools.test.ts:49:20
src/__tests__/catalog-tools.test.ts > list_specialists tool > filters by division: src/__tests__/catalog-tools.test.ts#L39
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog-tools.test.ts:39:28
src/__tests__/catalog-tools.test.ts > list_specialists tool > returns formatted output with all specialists: src/__tests__/catalog-tools.test.ts#L28
AssertionError: expected 0 to be greater than 0 ❯ src/__tests__/catalog-tools.test.ts:28:28
build-and-test (bun, 1.3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test (node, 22)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test (node, 26)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/