Enforce timestamp-prefixed migration filenames generated via drizzle.config.ts / src/db/migrate.ts

[Jagadeeshftw]

📌 Description

Drizzle migrations under the folder configured in drizzle.config.ts should follow a consistent timestamp-prefixed naming convention so ordering is unambiguous; nothing currently enforces this, so a manually-added or renamed migration file could silently break apply order.

🧩 Requirements and context

• Add a lint/check script that verifies every migration filename in the configured migrations folder matches the expected timestamp-prefixed pattern.
• Run the check in CI (.github/workflows/ci.yml) so a violation fails the build, not just local dev.
• Document the naming convention near the migrations folder or in README.md.

🛠️ Suggested execution

1. Write a small script that reads the migrations directory referenced by drizzle.config.ts and validates filenames against the pattern.
2. Wire the script into package.json scripts and into CI.
3. Add a test with a deliberately misnamed fixture filename asserting the check fails.

✅ Acceptance criteria

• A correctly-named migration set passes the check.
• An incorrectly-named migration file fails the check with a clear message.
• The check runs in CI.

🔒 Security notes

None — this is a correctness/ordering safeguard for migrations, not a security control.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Devadakene]

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

I am skilled enough to implement this issue having worked on similar issues in the past

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

[fahatadam]

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

Good day Maintainer can you please assign me this issue

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

[Jagadeeshftw]

Assigned @fahatadam to this issue. Please open a PR referencing this issue (e.g. Closes #180) when you're ready. If you have questions along the way, feel free to join our contributor chat: https://t.me/+vTbe0hOUKrFhNTJl

[drips-wave]

Congratulations, @fahatadam! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @fahatadam: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[Jagadeeshftw]

Thanks for applying here. Please also join our Telegram group here: https://t.me/+vTbe0hOUKrFhNTJl. It helps us keep communication clear while we review contributions.