feat: implement Release Please workflow and update configuration

Author: dermatz

.github/workflows/release-please.yml

@@ -0,0 +1,26 @@
+name: Release Please
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Run Release Please
+        uses: googleapis/release-please-action@v4
+        with:
+          # The GitHub token for creating releases and pull requests
+          token: ${{ secrets.GITHUB_TOKEN }}
+          
+          # Path to release-please-config.json
+          config-file: release-please-config.json
+          
+          # Path to .release-please-manifest.json
+          manifest-file: .release-please-manifest.json

.github/workflows/release.yml

@@ -0,0 +1,3 @@
+{
+  ".": "0.3.1"
+}

.release-please-manifest.json

@@ -11,6 +11,71 @@ We appreciate your interest in contributing to MageForge! Please follow the guid
 
 ---
 
+## Commit Message Guidelines
+
+We use [Conventional Commits](https://www.conventionalcommits.org/) for automated changelog generation and semantic versioning via [Release Please](https://github.com/googleapis/release-please).
+
+### For Contributors (Pull Requests)
+
+**PR Title Format** (Required): Your PR title **must** follow Conventional Commits format:
+
+```
+<type>: <description>
+
+Examples:
+✅ feat: add Hyvä compatibility check command
+✅ fix: resolve npm installation issue
+✅ docs: update README with new examples
+✅ refactor: simplify theme builder logic
+✅ perf: optimize static file cleaning
+
+❌ Add new feature (missing type)
+❌ Fixed bug (missing colon)
+```
+
+**Commit Types**:
+- `feat:` - New feature (minor version bump: 0.3.0 → 0.4.0)
+- `fix:` - Bug fix (patch version bump: 0.3.0 → 0.3.1)
+- `refactor:` - Code refactoring (no version bump by default)
+- `docs:` - Documentation updates (patch version bump)
+- `perf:` - Performance improvements (patch version bump)
+- `style:` - Code style changes (no version bump)
+- `test:` - Test updates (no version bump)
+- `chore:` - Maintenance tasks (no version bump)
+
+**Breaking Changes**: Add `!` after the type for major version bumps:
+```
+feat!: remove legacy theme builder API
+fix!: change command argument order
+```
+
+**Individual Commits**: Your individual commits within the PR can use any format you prefer. We use **squash-merge**, so only the PR title becomes the commit message in the `main` branch.
+
+### For Maintainers (Direct Commits)
+
+When committing directly to `main` (e.g., hotfixes, urgent documentation updates), **all commits must follow Conventional Commits format**:
+
+```bash
+# Hotfix example
+git commit -m "fix: resolve critical security vulnerability in npm dependencies"
+
+# Documentation update
+git commit -m "docs: add troubleshooting section to releases.md"
+
+# Chore example
+git commit -m "chore: update GitHub Actions to latest versions"
+```
+
+### Merge Strategy
+
+All pull requests are merged using **squash-merge** to maintain a clean, linear git history. This means:
+- ✅ Only one commit per PR in `main` branch
+- ✅ PR title becomes the commit message
+- ✅ All PR commits are squashed into a single commit
+- ✅ Easier to follow project history and revert changes if needed
+
+---
+
 ## Coding Standards
 
 - **Magento Coding Standards**: Adhere to the Magento Coding Standards throughout your code.

CONTRIBUTING.md

@@ -2,7 +2,8 @@
 
 ![Mageforge Hero](./.github/assets/mageforge-hero.jpg)
 
-[![CodeFactor](https://www.codefactor.io/repository/github/openforgeproject/mageforge/badge)](https://www.codefactor.io/repository/github/openforgeproject/mageforge) [![Magento Compatibility Test](https://github.com/OpenForgeProject/mageforge/actions/workflows/magento-compatibility.yml/badge.svg)](https://github.com/OpenForgeProject/mageforge/actions/workflows/magento-compatibility.yml)
+[![Release](https://img.shields.io/github/v/release/OpenForgeProject/mageforge)](https://github.com/OpenForgeProject/mageforge/releases) [![License](https://img.shields.io/badge/license-GPL--3.0-blue.svg)](LICENSE) [![CodeFactor](https://www.codefactor.io/repository/github/openforgeproject/mageforge/badge)](https://www.codefactor.io/repository/github/openforgeproject/mageforge) [![Magento Compatibility Test](https://github.com/OpenForgeProject/mageforge/actions/workflows/magento-compatibility.yml/badge.svg)](https://github.com/OpenForgeProject/mageforge/actions/workflows/magento-compatibility.yml)
+
 
 MageForge is a powerful CLI front-end development toolkit for Magento 2 that simplifies theme development workflows. It provides tools for many types of Magento themes and can be easily extended for your custom theme. With MageForge, themes can be built lightning fast, without your developers having to worry about the details. MageForge eliminates complex configuration requirements and significantly reduces setup time, allowing Magento developers to focus on creative aspects instead of struggling with build processes.
 

README.md

@@ -1,6 +1,7 @@
 {
   "name": "openforgeproject/mageforge",
   "description": "Magento 2 module for frontend wizardry~",
+  "version": "0.3.1",
   "license": "GPL-3.0",
   "type": "magento2-module",
   "autoload": {