CI/CD: Release — add semantic versioning and changelog generation

[Hexstar-labs]

Description:
There is no versioning or changelog process.

Tasks:

• Add release-please GitHub Action for automated semantic versioning
• Configure conventional commits enforcement via commitlint + husky pre-commit hook
• Auto-generate CHANGELOG.md on each release
• Bump package.json versions in both apps on release
• Tag Docker images with the semantic version

---

[steph-crown]

@steph-crown has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'll autpmate the release process by implementing release-please, enforcing commitlint with husky, and ensuring both package.json and Docker tags sync with semantic versions.

Relevant experience

• CI/CD Automation: I've implemented automated release pipelines for monorepos using Semantic Release and Release Please.

• Developer Experience: I have large experience in setting up Git hooks and conventional commit enforcement to maintain clean, searchable changelogs.

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

[jaynomyaro]

@jaynomyaro has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi! I’m Jaynom, a full-stack developer with a background in blockchain. I would love to take on this issue. I have extensive experience in both frontend and backend development and am confident I can implement a clean solution. Could you please assign this to me?

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

[Babigdk]

@Babigdk has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’ll implement this feature end-to-end, ensuring it’s robust, scalable, and consistent with your existing patterns. I’ll also include appropriate testing to guarantee it works as expected.

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

[Nonso-Eze]

@Nonso-Eze has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Can I work on this issue

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

[drips-wave]

Congratulations, @Nonso-Eze! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Nonso-Eze: 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 🌊

[drips-wave]

This issue has been completed by @Nonso-Eze as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @Nonso-Eze: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.