Add automated database migration dry-run step to CI pipeline

[RUKAYAT-CODER]

Overview

The CI pipeline (.github/workflows/ci.yml) runs tests but does not validate TypeORM migrations against a real database. A broken migration is only discovered during deployment, potentially requiring a rollback under pressure.

Specifications

Features:

• Run typeorm migration:run against a PostgreSQL service container in CI.
• Fail the pipeline if the migration produces errors.

Tasks:

• Add a PostgreSQL service to the CI workflow.
• Add a CI step: npm run migration:run && npm run migration:revert (run then revert to verify both directions).
• Add migration:generate check: fail if running it would produce a new migration (schema drift).
• Update CONTRIBUTING.md with migration testing instructions.

Impacted Files:

• .github/workflows/ci.yml
• package.json (add migration scripts if missing)

Acceptance Criteria

• CI fails if any migration file produces an error.
• CI fails if model changes exist without a corresponding migration.
• Revert step confirms migrations are reversible.

[OsejiFabian]

@OsejiFabian has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

PLEASE I WOULD LIKE TO WORK ON
THIS ISSUE ETA 4HRS

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OsejiFabian to this issue.

[Meme11030]

@Meme11030 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Rina please assign me just one issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Meme11030 to this issue.

[GazzyLee]

@GazzyLee has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

gm gm boss, I’d be happy to take this on. I can implement full SEP-10 authentication support, including challenge transaction handling, wallet-based signing, JWT lifecycle management, and tests to ensure reliable authentication with SEP-10 compliant anchors. ETD is in 4 hours tops, please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GazzyLee to this issue.

[pharwasz]

@pharwasz has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I can fix this within the short rush hour

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pharwasz to this issue.

[collinsezedike]

@collinsezedike has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey Rukayat, I'd like to help with this issue

My approach would to:

• Add a PostgreSQL service container to .github/workflows/ci.yml
• New CI step running migration:run then migration:revert against it, confirming both directions succeed cleanly
• Add a schema drift check: run migration:generate against the test database after migrations apply, and fail the pipeline if it would produce a new migration file, meaning the entities and migrations are out of sync
• Add any missing migration scripts to package.json
• Update CONTRIBUTING.md with instructions for running and testing migrations locally

Happy to start as soon as I'm assigned.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @collinsezedike to this issue.