Skip to content

fix: rename syntax → spec_version in example seed#5

Merged
zeevdr merged 1 commit intomainfrom
fix/spec-version-rename
Apr 20, 2026
Merged

fix: rename syntax → spec_version in example seed#5
zeevdr merged 1 commit intomainfrom
fix/spec-version-rename

Conversation

@zeevdr
Copy link
Copy Markdown
Member

@zeevdr zeevdr commented Apr 20, 2026

Post-decree#118 cleanup. The top-level YAML key syntax: was renamed to spec_version: in the decree schema/config/seed format. Without this change, decree seed examples/seed.yaml against a decree built from main fails with:

spec_version is required

Generated stubs (schema_service_pb2.pyi) still reference the old name in a doc comment — will regenerate on the next decree release bump.

Test plan

  • decree seed examples/seed.yaml against a locally-built decree from main succeeds (manual check recommended)

🤖 Generated with Claude Code

Follows decree#118 which renamed the top-level seed/schema/config YAML
key from `syntax:` to `spec_version:`. Without this, `decree seed
examples/seed.yaml` against a decree built from main fails at parse.

Generated stubs (schema_service_pb2.pyi) still reference the old name
in a doc comment — will regenerate on the next decree release bump.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zeevdr zeevdr merged commit 9daa685 into main Apr 20, 2026
9 checks passed
@zeevdr zeevdr deleted the fix/spec-version-rename branch April 20, 2026 11:16
zeevdr added a commit that referenced this pull request Apr 21, 2026
Follows decree#118 which renamed the top-level seed/schema/config YAML
key from `syntax:` to `spec_version:`. Without this, `decree seed
examples/seed.yaml` against a decree built from main fails at parse.

Generated stubs (schema_service_pb2.pyi) still reference the old name
in a doc comment — will regenerate on the next decree release bump.

Co-authored-by: zeevdr <zeevdr@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

2 participants