Automate release creation via GitHub Action (instead of local machines)

[Chandanydv1234]

Currently releases are being built and published from local machines. We should move this to an automated, manually-triggered GitHub Action so releases are reproducible and not dependent on any individual's local environment.
Proposed workflow:
A single, manually-triggered (workflow_dispatch) release action that:

1. Runs the test suite
2. Builds the project (mvn package)
3. Copies the packaged artifact from the assembly/target directory
4. Publishes it as a GitHub Release

Acceptance criteria:

1. Release can be triggered manually from the GitHub Actions UI
2. Tests must pass before a release is created
3. The release artifact is attached to a GitHub Release automatically
4. No local-machine steps required in the release process

Notes:

Should be testable on a personal/fork repo before rolling out.

[akandeadedayo01]

Hi @Chandanydv1234 , I’d like to work on this.

I can add a GitHub Actions workflow to automate release creation, following the existing release process and documenting any required tokens, tags, or maintainer steps.

This fits my DevOps background around release automation, CI/CD, and reducing manual release work.

Please assign this to me.

[sonalgoyal]

@akandeadedayo01 sure thanks! Looking forward to your pr.

[akandeadedayo01]

@sonalgoyal Still trying to work on this but for whatever reason after forking this repo; I've been unable to clone it on my workstation, always get stuck at 11%, I don't know why. Has this ever hapened before?