Skip to content

fix(archive): stop failing on specs that were already synced before archiving #1376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
clay-good merged 3 commits into from
Jul 17, 2026
Merged

fix(archive): stop failing on specs that were already synced before archiving #1376

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c352ec4
fix(archive): treat already-synced ADDED requirements as a no-op
clay-good Jul 16, 2026
fbee80f
Merge origin/main into fix/archive-added-idempotent-after-sync
clay-good Jul 17, 2026
07b490b
Restore pnpm-lock.yaml from main (accidental v6 rewrite during merge)
clay-good Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .changeset/idempotent-added-archive.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
"@fission-ai/openspec": patch
---

### Bug Fixes

- **Archive after early sync** — `openspec archive` no longer fails with `ADDED failed … already exists` when a change's specs were already synced to the main specs before archiving (the early-sync pattern from the `sync` workflow). If an ADDED requirement already exists in the target spec with identical content, applying it is treated as a no-op; a same-named requirement with different content still aborts the archive as a genuine conflict (#1332).
Loading
Loading