chore: add changeset for project config and schema commands #530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a changeset for the changes since v0.21.0:
New Features
Project-level configuration — Configure OpenSpec behavior per-project via
openspec/config.yaml, including custom rules injection, context files, and schema resolution settings (feat(config): add project-level configuration via openspec/config.yaml #499)Project-local schemas — Define custom artifact schemas within your project's
openspec/schemas/directory for project-specific workflows (feat(resolver): add project-local schema support #522)Schema management commands — New
openspec schemacommands (list,show,export,validate) for inspecting and managing artifact schemas (experimental) (feat(cli): add schema management commands #525)Bug Fixes
rulesfield in project configuration (fix(config): handle null rules field in project config #529)Version bump:
minor(new features)Summary by CodeRabbit
New Features
Bug Fixes
✏️ Tip: You can customize this high-level summary in your review settings.