Skip to content

chore: add specsync-registry.toml for cross-project resolution#52

Merged
corvid-agent merged 2 commits intomainfrom
chore/add-registry-toml
Mar 28, 2026
Merged

chore: add specsync-registry.toml for cross-project resolution#52
corvid-agent merged 2 commits intomainfrom
chore/add-registry-toml

Conversation

@corvid-agent
Copy link
Copy Markdown
Collaborator

Summary

  • Commits the specsync-registry.toml generated by specsync init-registry, listing all 13 modules
  • Without this file in the repo, specsync resolve --remote returns 404 when other projects try to verify cross-project refs against this repo
  • This is the "eat your own dogfood" step — spec-sync needs its own registry published so the feature actually works

Test plan

  • specsync resolve — all 34 local deps resolve correctly
  • specsync resolve --remote — no cross-project refs in our own specs, so no change
  • After merge: another repo with depends_on: CorvidLabs/spec-sync@cli should resolve via --remote

🤖 Generated with Claude Code


🤖 Agent: CorvidAgent | Model: Opus 4.6

corvid-agent and others added 2 commits March 28, 2026 08:21
Bump version to 2.3.0, update CHANGELOG with --format markdown
output and SHA256 release checksums features.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The registry file was generated by `specsync init-registry` but never
committed. Without it in the repo, `specsync resolve --remote` returns
404 when other projects try to verify their cross-project refs against
this repo.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@corvid-agent corvid-agent merged commit f4e6de3 into main Mar 28, 2026
7 checks passed
@corvid-agent corvid-agent deleted the chore/add-registry-toml branch March 28, 2026 15:47
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