Add manual workflow_dispatch workflow for version bumping and tagging

[Copilot]

No automated way existed to bump the project version, commit, and push a tag — a prerequisite for triggering the existing tag-based publish pipeline.

Changes

• .github/workflows/bump-version.yml — new manually-triggered workflow:
  • workflow_dispatch with a bump_type choice input (patch / minor / major, default: patch)
  • Configures github-actions[bot] as the Git committer
  • Runs npm version <type> with commit message format chore(release): %s
  • Pushes via git push origin HEAD --follow-tags to deliver both the version bump commit and the new tag
  • permissions: contents: write at workflow level to authorize the push

- name: Bump version
  run: npm version ${{ github.event.inputs.bump_type }} -m "chore(release): %s"

- name: Push commit and tag
  run: git push origin HEAD --follow-tags

The newly pushed v*.*.* tag will automatically trigger the existing release.yml publish pipeline.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add manual workflow for version bump and tagging</issue_title>
<issue_description>We need a new GitHub Actions workflow that can be triggered manually via the GitHub UI (workflow_dispatch). The sole purpose of this workflow is to bump the project version, commit the change, and push the new tag.

Our existing CI/CD pipelines are already configured to react to new tags and will handle the build and publish processes automatically.

Acceptance Criteria:

• Create a new workflow file (e.g., .github/workflows/bump-version.yml).
• The workflow must use on: workflow_dispatch with an input parameter to select the version bump type (patch, minor, major — default: patch).
• The job should run on ubuntu-latest.
• It must check out the repository using actions/checkout.
• It must configure a Git bot user (e.g., github-actions[bot]).
• It must bump the version using standard Node.js tools (npm version <type>).
• It must push the new commit (with the updated package.json) and the newly created tag back to the repository (git push --follow-tags).
• The workflow must explicitly include permissions: contents: write to allow pushing commits and tags.

Notes for implementation:
Make sure the commit message generated by the version bump is clean (e.g., chore(release): %s) so it integrates well with our commit history.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add manual workflow for version bump and tagging #32

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.