Skip to content

Suggested test: claude/update-issue-schema-registration-regression #20860

Closed as not planned

Description

@github-actions

Motivation

Link to the gh-aw PR: github/gh-aw#66784 — Fixed update_issue's MCP tool schema to remove a top-level anyOf that Anthropic rejects during tool registration, while preserving the handler's "at least one update field required" validation. No existing test exercises update_issue with the Claude engine.

Proposed test

  • Workflow file: test-claude-update-issue.md (already exists)
  • Trigger: issues: [opened, reopened] (existing pattern)
  • Engine: claude
  • Safe output: update-issue
  • Variant: standard

Minimal test prompt sketch

Existing test-claude-update-issue.md already covers the happy path. The gap is regression coverage for tool registration itself — i.e. confirming the Claude engine's MCP session successfully registers the update_issue tool without an Anthropic API schema-validation error. This is best verified by confirming the existing test's agent step log shows no tool-registration failure, rather than a new workflow.

New fixtures or secrets needed

None.

Notes

This is largely already covered by the existing test-claude-update-issue.md dispatch (its continued success after the fix is itself the regression signal). Flagging here mainly because it's a Claude-specific engine compatibility fix that could otherwise silently regress — recommend the e2e harness maintainer confirm the existing test's log checker would actually catch an "Anthropic rejects schema with anyOf" tool-registration failure (vs. just checking for safe-output presence) before closing this as already covered.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 110.9 AIC · ⌖ 6.34 AIC · ⊞ 8.6K · ◷

Activity

  1. dsyme commented on Oct 24, 2026

    @dsyme
    Collaborator

    Closing during the 2026-10-24 E2E triage: this is a narrow bug-regression, schema/default, alias, or rejection case better covered in github/gh-aw unit or integration tests. The retained E2E phases prioritize new safe outputs, unrepresented frontmatter, and behavior requiring live Actions/GitHub state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions