Skip to content

fix: reconcile stale extraction artifacts safely - #246

Merged
Alexander Zaslonov (azaslonov) merged 1 commit into
mainfrom
fix/106-clean-stale-artifacts
Aug 27, 2026
Merged

fix: reconcile stale extraction artifacts safely#246
Alexander Zaslonov (azaslonov) merged 1 commit into
mainfrom
fix/106-clean-stale-artifacts

Conversation

@azaslonov

Copy link
Copy Markdown
Member

Summary

  • add opt-in --remove-stale extraction cleanup and enable it in generated CI pipelines
  • stage extraction output and reconcile only managed artifacts in the selected filter and workspace scope
  • preserve stale artifacts after partial extraction and skip commits after fatal extraction
  • propagate API, product, gateway, and workspace supplemental failures into cleanup gating
  • use recoverable candidate/backup directory swaps with deterministic failure coverage
  • reconcile specifications, policies, wikis, and association files while preserving unmanaged content

Validation

  • npm run build
  • npm run lint
  • npm test (1,142 tests)
  • git diff --check
  • constitution review: approved with no findings

Related Issue(s)

Closes #106

@azaslonov
Alexander Zaslonov (azaslonov) merged commit f897cc8 into main Aug 27, 2026
6 checks passed
@azaslonov
Alexander Zaslonov (azaslonov) deleted the fix/106-clean-stale-artifacts branch August 27, 2026 23:54
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.

Extract does not remove stale artifacts, causing Publish delete-unmatched to republish deleted APIM resources

2 participants