Skip to content

manifest: adopt rolling v0 schema - #2

Merged
Jairus (JairusSW) merged 1 commit into
mainfrom
codex/schema-v0
Jul 31, 2026
Merged

manifest: adopt rolling v0 schema#2
Jairus (JairusSW) merged 1 commit into
mainfrom
codex/schema-v0

Conversation

@JairusSW

Copy link
Copy Markdown
Member

What changed

  • adopts the rolling https://wago.sh/v0/schema.json manifest
  • removes named schema generations and manifest-owned capability grants
  • normalizes the package and embedded extension identity to 0.0.0
  • updates consumer examples to keep exact versions and reviewed capabilities in wago-lock.json where applicable

Why

The plugin ecosystem is still pre-release. The breaking v0 manifest now keeps wago.json limited to plugin intent and semantic-version constraints, while the lockfile owns exact resolution, capabilities, budgets, and plugin config.

Validation

  • go test ./...
  • manifest validation with AJV against the proposed Wago v0 schema

Why:
- align plugin publishing with the breaking pre-release manifest model

What:
- use the hosted v0 schema and 0.0.0 package identity
- keep reviewed capabilities and exact versions out of wago.json

Proof:
- go test ./...
- manifest validates against the v0 JSON Schema

Docs:
- consumer examples updated where this repository documents manifest authority
@JairusSW
Jairus (JairusSW) marked this pull request as ready for review July 31, 2026 01:27
@JairusSW
Jairus (JairusSW) merged commit 0444773 into main Jul 31, 2026
1 check 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