reuse existing workflow

[kasif-adnan]

Description

Issues Resolved

Type of Change

Our release process assumes you are using Conventional Commit messages.

The most important prefixes you should have in mind are:

• _fix_: which represents bug fixes, and correlates to a SemVer patch.
• _feat_: which represents a new feature, and correlates to a SemVer minor.
• _feat!_:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a major version change.

If you have not included a conventional commit message this can be fixed on merge.

Check List

• [ ] All tests pass.
• [ ] All style checks pass.
• [ ] Functionality includes testing.
• [ ] Functionality has been documented in the README if applicable
• [ ] Commit message includes a Conventional Commit Message

[xorima]

How does this release process for conventional commits work as I cannot see reference within this PR for them?

[kasif-adnan]

How does this release process for conventional commits work as I cannot see reference within this PR for them?

We have it merged on the main branch