From 99b8edf685727ad83ac09f67f038e6bc9a64f8ee Mon Sep 17 00:00:00 2001 From: Jonathan Hefner Date: Mon, 16 Mar 2026 12:04:06 -0500 Subject: [PATCH] Add runtime version example to `compatibility` field MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a third example showing a Python version requirement alongside `uv`. This complements the existing examples (product targeting and system tool requirements) by demonstrating version-pinned runtime requirements — the kind of non-obvious constraint that the `compatibility` field is useful for. Co-Authored-By: Claude Opus 4.6 (1M context) --- docs/specification.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/specification.mdx b/docs/specification.mdx index 6fc8db8..57cd821 100644 --- a/docs/specification.mdx +++ b/docs/specification.mdx @@ -135,6 +135,9 @@ compatibility: Designed for Claude Code (or similar products) ```yaml compatibility: Requires git, docker, jq, and access to the internet ``` +```yaml +compatibility: Requires Python 3.14+ and uv +```