Skip to content

Releases: CorvidLabs/spec-sync

v3.2.0

31 Mar 02:44
07a5ceb

Choose a tag to compare

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

Full Changelog: v3.1.0...v3.2.0

v3.1.0

31 Mar 02:21
5fe06f4

Choose a tag to compare

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 agents hook target generates AGENTS.md files, 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

Full Changelog: v3.0.0...v3.1.0

v3.0.0 — VS Code Extension + Full Editor Integration

31 Mar 00:12
c3a869d

Choose a tag to compare

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, or specs/ 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

Full Changelog: v2.5.0...v3.0.0

v2.5.0 — Schema Column Validation, PHP & Ruby

30 Mar 13:23
5f8c144

Choose a tag to compare

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

Full Changelog: v2.4.0...v2.5.0

v2.4.0

28 Mar 17:49
28f6496

Choose a tag to compare

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

Full Changelog: v2.3.3...v2.4.0

What's Changed

Full Changelog: v2.3.3...v2.4.0

v2.3.3

28 Mar 17:02
1e06124

Choose a tag to compare

What's Changed

Full Changelog: v2.3.1...v2.3.3

v2.3.2

28 Mar 16:19

Choose a tag to compare

What's Changed

Full Changelog: v2.3.1...v2.3.2

v2.3.1

28 Mar 15:58
21a98dc

Choose a tag to compare

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

28 Mar 15:26
0b57dd4

Choose a tag to compare

What's Changed

Full Changelog: v2.2.1...v2.3.0

v2.2.1

25 Mar 15:40
2a69445

Choose a tag to compare

What's New

Added

  • Manifest-aware module detection — parses Package.swift, Cargo.toml, build.gradle.kts, package.json, pubspec.yaml, go.mod, and pyproject.toml to 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 in specsync.json for explicit module groupings
  • Language-specific spec templatesgenerate and --fix produce 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
  • check command 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

Full Changelog: v2.2.0...v2.2.1