Skip to content

fix(core): distinguish upgrade readiness from advisories#137

Merged
jb-thery merged 1 commit into
developfrom
feature/upgrade-readiness-advisories
Jul 18, 2026
Merged

fix(core): distinguish upgrade readiness from advisories#137
jb-thery merged 1 commit into
developfrom
feature/upgrade-readiness-advisories

Conversation

@jb-thery

Copy link
Copy Markdown
Member

Summary

  • distinguish operational upgrade readiness from independent privacy warnings
  • expose privacy compliance and actionable advisories in text and JSON output
  • document when reindexing is required and when a healthy index should be kept

Continuity validation

  • pnpm validate passes, including 498 Core tests
  • old schema, missing manifest, old config defaults, interrupted staged rebuilds, and advisory-only states are covered
  • both existing PAC indexes report status=current and ready=true while preserving their security advisories

Release highlights:
- keep retrieval ready after safe migrations when only privacy warnings remain

Release details:
- **Upgrade DX:** report security follow-ups as non-blocking advisories
- **Continuity:** preserve strict doctor checks while avoiding unnecessary reindex loops

Verification:
- pass pnpm validate
- verify both PAC indexes report current and ready with their advisories
@jb-thery
jb-thery merged commit 260b0f7 into develop Jul 18, 2026
14 of 15 checks passed
@jb-thery
jb-thery deleted the feature/upgrade-readiness-advisories branch July 18, 2026 13: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