Releases: CorvidLabs/spec-sync
v3.2.0
What's Changed
- Fix: Replace checkboxes with plain bullets in requirements files and template
- Feat: Add companion file context and update prompts to all agent hooks
- Bump version to 3.2.0
Full Changelog: v3.1.0...v3.2.0
What's Changed
- fix: replace checkboxes with plain bullets in requirements files by @corvid-agent in #88
- Release v3.2.0 by @corvid-agent in #89
Full Changelog: v3.1.0...v3.2.0
v3.1.0
What's New
Requirements Companion Files
- Requirements sections now live in dedicated companion files (
requirements.md) alongside each spec, keeping specs focused while preserving structured requirements tracking - All 15 existing specs populated with real requirements content
AGENTS.md Hook Target
- New
agentshook target generatesAGENTS.mdfiles, giving AI agents project-aware context automatically
Other
- Requirements added as a default required section (v3.1.0)
Full Changelog: v3.0.0...v3.1.0
What's Changed
- feat: add Requirements as default required section (v3.1.0) by @corvid-agent in #82
- feat: add agents (AGENTS.md) hook target by @corvid-agent in #83
- feat: move Requirements to companion file (requirements.md) by @corvid-agent in #84
- feat: move Requirements to companion file (v3.2.0) by @corvid-agent in #85
- feat: populate all 15 requirements companion files by @corvid-agent in #86
- feat: requirements companion file + AGENTS.md hook target (v3.1.0) by @corvid-agent in #87
Full Changelog: v3.0.0...v3.1.0
v3.0.0 — VS Code Extension + Full Editor Integration
Highlights
SpecSync now has a first-class VS Code extension — inline diagnostics, quality scores, coverage reports, and validate-on-save, all powered by the CLI.
Added
- VS Code extension (
corvidlabs.specsync) — published on the VS Code Marketplace- Inline diagnostics mapped to spec files with proper severity
- CodeLens quality scores (0–100 with letter grades) displayed above spec files
- Coverage webview with theme-aware HTML report
- Scoring webview with per-spec quality breakdown and suggestions
- Five commands: Validate, Coverage, Score, Generate, Initialize
- Status bar indicator with pass/fail/error/syncing states
- Validate-on-save (debounced 500ms)
- Configurable settings:
specsync.binaryPath,specsync.validateOnSave,specsync.showInlineScores - Auto-activates in workspaces with
specsync.json,.specsync.toml, orspecs/directory
Breaking Changes
- Major version bump to v3. GitHub Action users should update to
CorvidLabs/spec-sync@v3.
Full changelog: https://github.com/CorvidLabs/spec-sync/blob/main/CHANGELOG.md
What's Changed
- feat: VS Code extension MVP by @corvid-agent in #68
- release: v3.0.0 — VS Code extension + full editor integration by @corvid-agent in #79
- feat: VS Code extension MVP with full CLI integration by @corvid-agent in #80
Full Changelog: v2.5.0...v3.0.0
v2.5.0 — Schema Column Validation, PHP & Ruby
What's New
Schema Column Validation
SpecSync now parses SQL migrations (CREATE TABLE, ALTER TABLE ADD COLUMN) and validates documented columns in spec ### Schema sections against the actual database schema. Catches:
- Phantom columns — documented in spec but missing from schema
- Undocumented columns — in schema but not in spec
- Type mismatches — column type drift between spec and migrations
Opt-in via schema_dir in specsync.json.
Destructive DDL Support
Migration parser correctly handles DROP TABLE, ALTER TABLE DROP COLUMN, ALTER TABLE RENAME TO, and ALTER TABLE RENAME COLUMN.
PHP Language Support
Full export extraction: classes, interfaces, traits, enums, public functions/constants, with visibility filtering and magic method exclusion.
Ruby Language Support
Full export extraction: classes, modules, public methods with visibility toggle tracking, attr_accessor/attr_reader/attr_writer, constants, and =begin/=end comment handling.
Also
- Multi-language migration file support (16 file types)
- Expanded test coverage for Go, Python, Java, C#, Dart parsers
- 100% spec coverage across all modules
- 11 languages now supported
Full Changelog: https://github.com/CorvidLabs/spec-sync/blob/main/CHANGELOG.md#250---2026-03-30
What's Changed
- Add downloads badge to README by @0xLeif in #62
- feat: schema column validation, PHP & Ruby language support by @corvid-agent in #63
- docs: achieve 100% spec coverage and fix all validation warnings by @corvid-agent in #64
- feat: schema column validation and multi-language export support by @corvid-agent in #65
- release: prep v2.5.0 by @corvid-agent in #67
Full Changelog: v2.4.0...v2.5.0
v2.4.0
What's Changed
Export Validation: Allowlist Model (#60)
Switched get_spec_symbols from a blocklist to an allowlist — only ### Exported ... subsections under ## Public API trigger export validation. All other subsections are treated as informational documentation.
This means specs can now document their full API surface in one place:
### Exported Functions/### Exported Types→ validated against code### API Endpoints/### Route Handlers/### Component API/### Configuration→ informational, no validation
Backwards-compatible — tables directly under ## Public API (no ### header) are still validated, and existing specs using ### Exported ... headers work exactly the same.
Full Changelog: v2.3.3...v2.4.0
What's Changed
- feat: switch export validation to allowlist model by @corvid-agent in #60
- chore: prepare v2.4.0 release by @corvid-agent in #61
Full Changelog: v2.3.3...v2.4.0
What's Changed
- feat: switch export validation to allowlist model by @corvid-agent in #60
- chore: prepare v2.4.0 release by @corvid-agent in #61
Full Changelog: v2.3.3...v2.4.0
v2.3.3
What's Changed
- fix: document missing exports and add spec:check to CI by @corvid-agent in #54
- feat: add manifest.spec.md for 100% file coverage by @corvid-agent in #55
- fix: quote github.token default in action.yml by @corvid-agent in #56
- chore: prepare v2.3.2 release by @corvid-agent in #57
- docs: populate all companion files with real content by @corvid-agent in #58
- chore: prepare v2.3.3 release by @corvid-agent in #59
Full Changelog: v2.3.1...v2.3.3
v2.3.2
What's Changed
- fix: document missing exports and add spec:check to CI by @corvid-agent in #54
- feat: add manifest.spec.md for 100% file coverage by @corvid-agent in #55
- fix: quote github.token default in action.yml by @corvid-agent in #56
Full Changelog: v2.3.1...v2.3.2
v2.3.1
What's Changed
- chore: add specsync-registry.toml for cross-project resolution by @corvid-agent in #52
- docs: cross-project refs page + missing CLI commands by @corvid-agent in #53
Full Changelog: v2.3.0...v2.3.1
v2.3.0
What's Changed
- feat: add --format markdown output and SHA256 release checksums by @corvid-agent in #50
- chore: prepare v2.3.0 release by @corvid-agent in #51
Full Changelog: v2.2.1...v2.3.0
v2.2.1
What's New
Added
- Manifest-aware module detection — parses
Package.swift,Cargo.toml,build.gradle.kts,package.json,pubspec.yaml,go.mod, andpyproject.tomlto auto-discover targets and source paths - Export granularity control —
"exportLevel": "type"limits exports to top-level type declarations instead of every member - Configurable module definitions —
"modules"section inspecsync.jsonfor explicit module groupings - Language-specific spec templates —
generateand--fixproduce Swift, Rust, Kotlin/Java, Go, and Python templates - AI context boundary awareness — generation prompt scopes to module-owned symbols only
Fixed
- Test file detection expanded with Swift/Kotlin/Java/C# patterns and well-known test directories
checkcommand no longer hangs on empty specs- Exit code 101 panics converted to friendly error messages
Full Changelog: v2.2.0...v2.2.1
What's Changed
- feat: manifest-aware modules, export granularity, and robustness fixes by @corvid-agent in #48
- chore: prepare v2.2.1 release by @corvid-agent in #49
Full Changelog: v2.2.0...v2.2.1