diff --git a/CHANGELOG.md b/CHANGELOG.md
index 72deba2..951cfdb 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,8 @@ The format is intentionally lightweight and human-readable. Group entries by rel
 
 ## Unreleased
 
+## v0.6.0 - 2026-03-12
+
 ### Added
 
 - Added modality-aware metrics and filters so stats, traces, recent requests, and the dashboard can distinguish `chat`, `image_generation`, and `image_editing`
diff --git a/RELEASES.md b/RELEASES.md
index 02285a2..097d917 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -21,11 +21,11 @@ This repo does not require a heavy release process. Use lightweight tags plus Gi
 ```bash
 git checkout main
 git pull --ff-only origin main
-git tag -a v0.5.0 -m "FoundryGate v0.5.0"
-git push origin v0.5.0
+git tag -a v0.6.0 -m "FoundryGate v0.6.0"
+git push origin v0.6.0
 ```
 
-Then open GitHub Releases and publish a release for `v0.5.0`.
+Then open GitHub Releases and publish a release for `v0.6.0`.
 
 ## Automation Baseline
 
@@ -54,11 +54,13 @@ The repo also includes [publish-dry-run](./.github/workflows/publish-dry-run.yml
 - `v0.3.0` is the first FoundryGate-branded release.
 - `v0.4.0` establishes the hardened routing baseline: request hooks, multi-dimensional scoring, route introspection, and the refined operator dashboard.
 - `v0.5.0` establishes the operator distribution baseline: image-provider contracts, Docker and GHCR packaging, PyPI workflow support, onboarding helpers, repo community standards, and cached release update checks.
+- `v0.6.0` establishes the modality-expansion baseline: image route previews, provider capability coverage, shared image request validation, and image policy presets.
 
 ## Planned Publishing Path
 
 - `v0.3.x`: GitHub Releases plus source checkout remain the default distribution path.
 - `v0.5.0`: Docker and PyPI publishing baseline is introduced through the release workflow and repo docs.
+- `v0.6.0`: modality-aware image routing becomes an explicit release line with provider inventory and image-policy guidance.
 - `v1.0.0`: keep GitHub Releases, Docker, and PyPI, and add a separate npm or TypeScript CLI package if the CLI surface is ready.
 
 The npm or TypeScript package should stay separate from the Python gateway core. It is meant for CLI-facing integrations, not for rewriting the service runtime.
diff --git a/foundrygate/__init__.py b/foundrygate/__init__.py
index 427fb4e..ebeb987 100644
--- a/foundrygate/__init__.py
+++ b/foundrygate/__init__.py
@@ -1,3 +1,3 @@
 """FoundryGate package."""
 
-__version__ = "0.5.0"
+__version__ = "0.6.0"
diff --git a/foundrygate/main.py b/foundrygate/main.py
index 53a593b..eb12cda 100644
--- a/foundrygate/main.py
+++ b/foundrygate/main.py
@@ -639,7 +639,7 @@ async def lifespan(app: FastAPI):
 
 app = FastAPI(
     title="FoundryGate",
-    version="0.5.0",
+    version="0.6.0",
     description="Local OpenAI-compatible routing gateway for OpenClaw and other clients.",
     lifespan=lifespan,
 )
diff --git a/pyproject.toml b/pyproject.toml
index ef699de..35f7dad 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "foundrygate"
-version = "0.5.0"
+version = "0.6.0"
 description = "Local OpenAI-compatible routing gateway for OpenClaw and other AI-native clients."
 readme = "README.md"
 license = "Apache-2.0"