[Feature] Automate Release Tag Creation and NPM Publish via publish.yml on Merging development into main

[omer-ayhan]

Problem Statement

Currently, when merging the development branch into main, no automation is triggered. This limits the team's ability to reliably and consistently create release tags and publish new package versions to npm. Manual intervention is required to create release tags and trigger the publishing process, which can be error-prone or overlooked.

Proposed Solution

• Set up and/or update the publish.yml GitHub Actions workflow.
• When a PR from development to main is merged:
  • Automatically create a new release tag, reading the new version from package.json.
  • After the release tag is created, have the action trigger npm publish using the newly created tag/version.
• Ensure the process only runs for merges from development into main (not for arbitrary PRs or manual pushes).
• Document the workflow in the repository for visibility.

Alternatives Considered

• Continue creating tags and publishing releases manually (less reliable and scalable).
• Use a different workflow file for publishing (less consolidated and maintainable).

Additional Context

• Example workflow: after merging a version PR from development to main, the workflow should detect the change, create a new tag using the version from package.json, and publish the new version to npm. This ensures releases reflect the code in main and npm is always up to date.
• This would improve automation reliability and reduce manual work during the release process.