Missing Alembic migration for webhook signature versioning

[usmanimamu17-create]

Labels / Complexity: database, schema · Trivial — 2 pts

Summary

The alembic/versions/0016_webhook_signature_versioning.py migration adds a signature_version column to webhook_deliveries, but the migration may have been applied inconsistently across environments. The WebhookDelivery model in app/models/webhook.py expects this column, but there is no CI check to verify migration consistency.

Proposal

• Verify the migration is present in alembic/versions/
• Add a CI step that runs alembic check to detect migration drift
• Ensure the migration is idempotent (safe to re-run)

Acceptance criteria

• alembic check passes in CI
• The signature_version column exists in production schema
• A test verifies the model matches the migration

Out of scope

Data backfill for existing records; assume signature_version defaults to 1.

Getting started

Files in scope:

• alembic/versions/0016_webhook_signature_versioning.py
• app/models/webhook.py

Build/test commands:

alembic check
pytest tests/test_migration_verification.py

Good first files to read: alembic/versions/0016_webhook_signature_versioning.py.

[Its-JrDev]

I'd like to work on this issue.

I understand the goal: verify migration consistency between the Alembic migration, the database schema, and the WebhookDelivery model.

I'll validate the existing migration, add the CI check, verify that the model and schema remain synchronized, and add the corresponding test to prevent future migration drift.

[gbengaeben]

Hi Maintainer
May I fix this issue

[DanielCharis1]

can i be assigned this

[grantfox-oss]

🦊 GrantFox — @DanielCharis1 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #242)
2. Your PR will be reviewed by the ApexChainx maintainers

Good luck! Track your progress on GrantFox.