Skip to content

Claude/cranky johnson #3

Claude/cranky johnson

Claude/cranky johnson #3

Triggered via pull request April 9, 2026 16:01
Status Failure
Total duration 2m 29s
Artifacts

ci.yml

on: pull_request
lint-and-test
1m 38s
lint-and-test
validate-commits
31s
validate-commits
integration-tests
1m 33s
integration-tests
Validate Docker builds
2m 24s
Validate Docker builds
enforce-dev-to-main
0s
enforce-dev-to-main
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 4 warnings
integration-tests
Process completed with exit code 1.
tests/integration/integration-validation.test.ts > Integration Validation (integration) > integration requirements > review requires only scm with optional pm: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'review.yaml': triggers.1.contextPipeline.2: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ Module.getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ tests/integration/integration-validation.test.ts:463:17
tests/integration/integration-validation.test.ts > Integration Validation (integration) > error message format > SCM errors contain provider reference: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'review.yaml': triggers.1.contextPipeline.2: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:417:19
tests/integration/integration-validation.test.ts > Integration Validation (integration) > persona-specific token validation > reviewer persona agents > review agent fails without reviewer token: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'review.yaml': triggers.1.contextPipeline.2: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:306:20
tests/integration/integration-validation.test.ts > Integration Validation (integration) > persona-specific token validation > reviewer persona agents > review agent passes with reviewer token: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'review.yaml': triggers.1.contextPipeline.2: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:296:20
tests/integration/integration-validation.test.ts > Integration Validation (integration) > persona-specific token validation > implementer persona agents > respond-to-pr-comment agent needs implementer token: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'respond-to-pr-comment.yaml': triggers.0.contextPipeline.4: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:281:20
tests/integration/integration-validation.test.ts > Integration Validation (integration) > persona-specific token validation > implementer persona agents > respond-to-ci agent needs implementer token: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'respond-to-ci.yaml': triggers.0.contextPipeline.3: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:281:20
tests/integration/integration-validation.test.ts > Integration Validation (integration) > persona-specific token validation > implementer persona agents > respond-to-review agent needs implementer token: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'respond-to-review.yaml': triggers.0.contextPipeline.4: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:281:20
tests/integration/integration-validation.test.ts > Integration Validation (integration) > SCM integration validation > fails when no SCM integration exists: src/agents/definitions/loader.ts#L44
Error: Invalid agent definition 'review.yaml': triggers.1.contextPipeline.2: Invalid enum value. Expected 'directoryListing' | 'contextFiles' | 'workItem' | 'prepopulateTodos' | 'prContext' | 'prConversation' | 'pipelineSnapshot' | 'alertingIssue', received 'squint' ❯ loadBuiltinDefinition src/agents/definitions/loader.ts:44:9 ❯ resolveAgentDefinition src/agents/definitions/loader.ts:116:9 ❯ getIntegrationRequirements src/triggers/shared/integration-validation.ts:41:14 ❯ Module.validateIntegrations src/triggers/shared/integration-validation.ts:158:23 ❯ tests/integration/integration-validation.test.ts:221:19
lint-and-test
Process completed with exit code 1.
validate-commits
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/
integration-tests
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/
lint-and-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-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/
Validate Docker builds
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 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/