docs: updated documentation

.gitignore

@@ -23,6 +23,7 @@ wheels/
 share/python-wheels/
 *.egg-info/
 .installed.cfg
+*.egg-info
 *.egg
 MANIFEST
 

.releaserc.yaml

@@ -8,8 +8,6 @@ plugins:
     - preset: conventionalcommits
       releaseRules:
         - type: feat
-          release: patch
-        - type: minor
           release: minor
         - type: impr
           release: patch
@@ -39,9 +37,6 @@ plugins:
           - type: feat
             section: "Features"
             hidden: false
-          - type: minor
-            section: "Minor Changes"
-            hidden: false
           - type: impr
             section: "Improvements"
             hidden: false

README.md

@@ -121,15 +121,10 @@ mypy --strict --ignore-missing-imports .
 bandit -c pyproject.toml -r -q .
 ```
 
-### Add new FeatureGroup
-Create new directory under `placeholder/feature_groups/` following the `my_plugin/` pattern.
-
 ## Related Documentation
 
 Guides for plugin development can be found in mloda-registry:
 
 - https://github.com/mloda-ai/mloda-registry/tree/main/docs/guides/
 
-## Architecture Overview
-
-- [Repository structure and relationships](https://github.com/mloda-ai/mloda-registry/blob/main/docs/architecture/00_repositories.md)
+This template includes pre-configured GitHub Actions workflows for testing, security scanning, and automated releases. See the [GitHub Workflows documentation](docs/github-workflows.md) for setup instructions and required secrets.

docs/github-workflows.md

@@ -0,0 +1,79 @@
+# GitHub Workflows
+
+This project uses three GitHub Actions workflows to automate testing, security scanning, and releases.
+
+## Test Workflow
+
+**File:** `.github/workflows/test.yml`
+
+**Triggers:**
+- Push to any branch
+- Pull request to `main`
+
+**Purpose:** Runs the full test suite using tox across multiple Python versions (3.10, 3.11, 3.12, 3.13). This includes pytest, ruff linting, mypy type checking, and bandit security analysis.
+
+**Requirements:** None. This workflow uses only public GitHub Actions and requires no secrets.
+
+## Security Scan Workflow
+
+**File:** `.github/workflows/security-scan.yaml`
+
+**Triggers:**
+- Scheduled: Every Monday at 9:00 AM UTC
+- Manual dispatch (can be triggered from any branch)
+
+**Purpose:** Performs CVE vulnerability scanning on the latest published release using pip-audit via tox. The workflow fetches the latest release version from GitHub and scans it for known vulnerabilities.
+
+**Requirements:** None. Uses only the default `GITHUB_TOKEN` with read permissions.
+
+## Release Workflow
+
+**File:** `.github/workflows/release.yaml`
+
+**Triggers:**
+- Manual dispatch only
+
+**Purpose:** Automates semantic versioning and publishing. The workflow:
+1. Analyzes commits using [semantic-release](https://semantic-release.gitbook.io/) to determine the next version
+2. Creates a GitHub release with changelog
+3. Updates version in `pyproject.toml`
+4. Builds and publishes the package to PyPI
+
+**Requirements:**
+- `SEMANTIC_RELEASE_TOKEN` - GitHub Personal Access Token with `repo` write permissions
+- `PYPI_API_TOKEN` - PyPI API token for package publishing
+
+**Prerequisites:** Commits must follow the [Conventional Commits](https://www.conventionalcommits.org/) format for semantic-release to determine version bumps:
+- `fix:` - Patch release (0.0.x)
+- `feat:` - Minor release (0.x.0)
+- `feat!:` or `BREAKING CHANGE:` - Major release (x.0.0)
+
+## Setting Up Secrets
+
+To configure the required secrets for the release workflow:
+
+### SEMANTIC_RELEASE_TOKEN
+
+1. Go to GitHub **Settings** > **Developer settings** > **Personal access tokens** > **Tokens (classic)**
+2. Click **Generate new token (classic)**
+3. Give it a descriptive name (e.g., "semantic-release")
+4. Select the `repo` scope (full control of private repositories)
+5. Click **Generate token** and copy the token
+6. In your repository, go to **Settings** > **Secrets and variables** > **Actions**
+7. Click **New repository secret**
+8. Name: `SEMANTIC_RELEASE_TOKEN`
+9. Value: Paste the token
+10. Click **Add secret**
+
+### PYPI_API_TOKEN
+
+1. Log in to [PyPI](https://pypi.org/)
+2. Go to **Account settings** > **API tokens**
+3. Click **Add API token**
+4. Give it a descriptive name and scope it to your project (recommended) or all projects
+5. Click **Create token** and copy the token
+6. In your repository, go to **Settings** > **Secrets and variables** > **Actions**
+7. Click **New repository secret**
+8. Name: `PYPI_API_TOKEN`
+9. Value: Paste the token (starts with `pypi-`)
+10. Click **Add secret**