fix: try fix semantic versioning (#912)

* fix: try fix semantic versioning

* update README to state that conventional commits is only needed for PR title

Author: Logende

.github/workflows/github-pages.yml

@@ -1,20 +1,29 @@
 name: Build and Deploy
 on:
-  push:
-    tags:
-      - 'v*'
+  workflow_run:
+    workflows: ["Create Release Tag"]
+    types:
+      - completed
+    branches:
+      - main
 permissions:
   contents: write
 jobs:
   build-and-deploy:
-    concurrency: ci-${{ github.ref }} # Recommended if you intend to make multiple deployments in quick succession.
+    concurrency: ci-${{ github.ref }}
     runs-on: ubuntu-latest
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
 
-      - name: Extract version from tag
-        run: echo "APP_VERSION=${GITHUB_REF_NAME#v}" >> $GITHUB_ENV
+      - name: Extract version from latest tag
+        run: |
+          git fetch --tags
+          VERSION=$(git describe --tags --abbrev=0 | sed 's/^v//')
+          echo "APP_VERSION=$VERSION" >> $GITHUB_ENV
 
       - name: Install and Build
         env:

.github/workflows/semantic-versioning.yml

@@ -12,7 +12,7 @@ jobs:
   tag:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
         with:
           fetch-depth: 0
 
@@ -21,6 +21,4 @@ jobs:
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           default_bump: patch
-          major_string_token: 'BREAKING CHANGE,!:'
-          minor_string_token: 'feat:'
-          patch_string_token: 'fix:,perf:,refactor:,docs:,chore:,test:'
+          custom_release_rules: 'breaking:major,feat:minor,fix:patch,perf:patch,refactor:patch,docs:patch,chore:patch,test:patch'

CONTRIBUTING.md

@@ -76,24 +76,14 @@ You can optionally open a **Draft Pull Request** earlier during development to g
 
 ---
 
-## Commit Message Convention
-
-This project follows [Conventional Commits](https://www.conventionalcommits.org/). Every commit message must start with a **type prefix**, followed by a short description written as a **verb phrase starting with a capital letter**.
-
-```
-<type>: <Verb> <subject>
-```
+## Pull Request Guidelines
 
-**Examples:**
-```
-feat: Add searchbar component
-fix: Resolve crash when schema is empty
-refactor: Extract validation logic into utility
-docs: Update contributing guide
-chore: Bump version to 2.1.0
-```
+- **Title:** Must follow the [Conventional Commits](https://www.conventionalcommits.org/) format — `<type>: <Verb> <subject>` — e.g. `feat: Add searchbar component`. This is required because the PR title is used as the squash merge commit message on `main`, from which the CI/CD pipeline automatically determines the semantic version bump and creates a release tag.
+- **Description:** Always explain **why** the change is needed, not just what was changed. Link the related issue.
+- **Scope:** Keep PRs focused on a single concern. Smaller PRs are reviewed faster and merged sooner.
+- **Discussion:** PRs are the primary place for code review discussion. Use inline comments and the general PR thread to ask questions and suggest improvements.
 
-**Type prefixes and their effect on versioning:**
+**PR title type prefixes and their effect on versioning:**
 
 | Prefix | Description | Version bump |
 |---|---|---|
@@ -104,18 +94,9 @@ chore: Bump version to 2.1.0
 | `docs:` | Documentation only | Patch |
 | `chore:` | Build process, dependencies, tooling | Patch |
 | `test:` | Adding or fixing tests | Patch |
-| `BREAKING CHANGE:` | Incompatible API change | Major (`X.0.0`) |
-
-The CI/CD pipeline uses these prefixes to automatically determine the next [semantic version](https://semver.org/) when commits are merged to `main`.
+| `breaking:` | Incompatible API change | Major (`X.0.0`) |
 
----
-
-## Pull Request Guidelines
-
-- **Title:** Use the same convention as commit messages — `<type>: <Verb> <subject>`.
-- **Description:** Always explain **why** the change is needed, not just what was changed. Link the related issue.
-- **Scope:** Keep PRs focused on a single concern. Smaller PRs are reviewed faster and merged sooner.
-- **Discussion:** PRs are the primary place for code review discussion. Use inline comments and the general PR thread to ask questions and suggest improvements.
+PRs are always merged via **squash merge**, so the PR title becomes the single commit message on `main`. Individual commit messages on your branch are not required to follow the Conventional Commits format, but should still start with a verb and clearly describe what was done, e.g. `Add validation for empty schema` — this helps reviewers follow your work in the PR.
 
 ---