Skip to content

chore: stamp config_version: v1 in agentfield-package.yaml#92

Merged
AbirAbbas merged 1 commit into
mainfrom
chore/manifest-config-version
Jul 8, 2026
Merged

chore: stamp config_version: v1 in agentfield-package.yaml#92
AbirAbbas merged 1 commit into
mainfrom
chore/manifest-config-version

Conversation

@AbirAbbas

Copy link
Copy Markdown
Collaborator

Now that the manifest format is versioned (config_version, added in the control plane), stamp SWE-AF's agentfield-package.yaml with the current schema version explicitly instead of relying on the implicit legacy default.

  • config_version: v1 — v1 is the current format; omitting the key means legacy v0. Being explicit future-proofs the manifest against format evolution and matches the guidance in docs/installing-agent-nodes.md.
  • No env changes. SWE-AF already declares the intended install surface: require_one_of for the LLM provider (bring either an Anthropic or an OpenRouter key) plus a required GH_TOKEN.

Part of a sweep stamping config_version: v1 across the agent-node manifests (pr-af, cloudsecurity-af, sec-af).

🤖 Generated with Claude Code

Declare the manifest schema version explicitly (v1 — the current format;
omitting it means legacy v0). Env requirements are unchanged: SWE-AF still
accepts either an Anthropic or an OpenRouter key via require_one_of and
requires GH_TOKEN.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@AbirAbbas AbirAbbas merged commit 546063f into main Jul 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant