Skip to content

fix(packaging): verify complete SQL migration inventory in release archives - #37

Merged
thecompez merged 1 commit into
mainfrom
audit/migration-package-parity-20261009
Oct 9, 2026
Merged

thecompez merged 1 commit into
mainfrom
audit/migration-package-parity-20261009

Conversation

@thecompez

Copy link
Copy Markdown
Member

Why

On the live OpenProof host, runtime/migrations is missing 0019_farcaster_profile_seed.sql while later migrations are present. Package scripts copy the source migrations, but previously did not validate the actual outputs.

What

  • Verify names and SHA-256 digests of every source SQL migration inside each finished Debian or bundle artifact.
  • Fail the respective packaging command when an artifact omits, alters, duplicates, or adds an unexpected migration.
  • Add seven independent fixture tests (including simulated Debian tar stream).
  • No changes to .github/workflows required: existing CI and release builders already invoke both packaging scripts.

Checks

  • Seven regression cases: pass.
  • JavaScript SDK tests and OpenAPI coverage: pass.
  • Python syntax and staged diff checks: pass.

Safety

  • Isolated branch. No production deployment or database writes. This prevents future package drift but does not by itself repair the production runtime: the database migration journal must be inspected read-only before restoring 0019.

@thecompez
thecompez marked this pull request as ready for review October 9, 2026 05:43
@thecompez
thecompez merged commit c3de7f1 into main Oct 9, 2026
3 checks passed
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