Automate version tagging on push to main

[Copilot]

Releases currently require manual version tagging. This adds automatic patch version tagging on pushes to main, triggering the existing release workflow.

Changes

• .github/workflows/cd.yml: New auto-tag job that:

  • Runs after tests pass on main branch pushes only
  • Increments patch version (v1.0.0 → v1.0.1) or starts at v0.1.0
  • Creates and pushes annotated tag, triggering the release job
  • Skips on tag pushes to prevent recursion

• CONTRIBUTING.md: Documents the automated release process and manual major/minor bump procedure

Workflow

graph LR
    A[Push to main] --> B[CI tests]
    B --> C[auto-tag job]
    C --> D[Tag push]
    D --> E[Docker build]
    E --> F[GitHub release]

Loading

Manual tags for major/minor versions bypass auto-tagging and go directly to release.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[FEATURE] pushes to main should result in a new release</issue_title>
<issue_description>## Problem Statement
Currently to create a new release involves manual steps, namely the tagging of the current version with an incremented version number

Proposed Solution

Can we update the push to main GitHub workflow to include the tagging of the release so that the release process starts.</issue_description>

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

• Fixes [FEATURE] pushes to main should result in a new release #15

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.