diff --git a/README.md b/README.md
index 3f28a89..02225fb 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ by `values.yaml`.
 ### OCI Registry (recommended)
 
 ```bash
-helm pull oci://ghcr.io/k8s-stuff/helm-framework --version 1.0.0
+helm pull oci://ghcr.io/k8s-stuff/helm-framework --version 1.1.0
 ```
 
 Or reference it directly as a dependency in your `Chart.yaml`:
@@ -33,7 +33,7 @@ Or reference it directly as a dependency in your `Chart.yaml`:
 ```yaml
 dependencies:
   - name: helm-framework
-    version: "1.0.0"
+    version: "1.1.0"
     repository: "oci://ghcr.io/k8s-stuff"
 ```
 
@@ -49,7 +49,7 @@ Then in your `Chart.yaml`:
 ```yaml
 dependencies:
   - name: helm-framework
-    version: "1.0.0"
+    version: "1.1.0"
     repository: "https://k8s-stuff.github.io/helm-framework"
 ```
 
diff --git a/plugins/helm-framework/.claude-plugin/plugin.json b/plugins/helm-framework/.claude-plugin/plugin.json
index d2995e4..7dff0f4 100644
--- a/plugins/helm-framework/.claude-plugin/plugin.json
+++ b/plugins/helm-framework/.claude-plugin/plugin.json
@@ -1,5 +1,5 @@
 {
   "name": "helm-framework",
   "description": "Scaffold and configure Helm charts that depend on the helm-framework library chart.",
-  "version": "1.0.0"
+  "version": "1.1.0"
 }
diff --git a/plugins/helm-framework/skills/helm-framework-migration/SKILL.md b/plugins/helm-framework/skills/helm-framework-migration/SKILL.md
index f270352..d3dbc03 100644
--- a/plugins/helm-framework/skills/helm-framework-migration/SKILL.md
+++ b/plugins/helm-framework/skills/helm-framework-migration/SKILL.md
@@ -8,7 +8,7 @@ description: "Migrate an existing hand-rolled Helm chart onto the helm-framework
 ## What this skill does
 
 Guides migrating an existing chart's hand-rolled templates onto
-`helm-framework` (v1.0.0 at generation time) safely. This is a distinct,
+`helm-framework` (v1.1.0 at generation time) safely. This is a distinct,
 harder job from scaffolding a new chart (see the `helm-framework` skill for
 that): `helm-framework` reads the consumer's flat `.Values` directly, with no
 `additionalProperties: false` enforcement, so a value nothing reads after
diff --git a/plugins/helm-framework/skills/helm-framework-migration/resources/migration-playbook.md b/plugins/helm-framework/skills/helm-framework-migration/resources/migration-playbook.md
index a3d8fdf..80da83c 100644
--- a/plugins/helm-framework/skills/helm-framework-migration/resources/migration-playbook.md
+++ b/plugins/helm-framework/skills/helm-framework-migration/resources/migration-playbook.md
@@ -1,7 +1,7 @@
 # helm-framework migration playbook
 
 Full detail for each of the five phases summarized in `SKILL.md`. Generated
-for version `1.0.0` — the version baked into Phase 0's comparison below.
+for version `1.1.0` — the version baked into Phase 0's comparison below.
 
 ## Phase 0 — Preflight (version currency)
 
@@ -9,7 +9,7 @@ Before touching anything, compare three versions:
 
 1. The consumer's own dependency pin in `Chart.yaml`
    (`dependencies[].version` for `helm-framework`).
-2. The version this skill was generated against: `1.0.0`.
+2. The version this skill was generated against: `1.1.0`.
 3. The newest published version, resolved in this order:
    - `helm show chart oci://ghcr.io/k8s-stuff/helm-framework`
    - falling back to the gh-pages index (`helm repo add` + `helm search repo
@@ -18,13 +18,13 @@ Before touching anything, compare three versions:
 
 Three outcomes:
 
-- **newest > `1.0.0` (this skill's own baked version)** — the installed
+- **newest > `1.1.0` (this skill's own baked version)** — the installed
   plugin is stale. Tell the user to update the plugin before proceeding, and
   warn explicitly that this playbook may not know about values added in
   newer releases.
 - **pin < newest** — bump the dependency *before* migrating, so the
   migration work isn't done twice against two different contracts.
-- **every lookup failed** — degrade to comparing the pin against `1.0.0`
+- **every lookup failed** — degrade to comparing the pin against `1.1.0`
   only, and state plainly that the upper bound could not be verified.
 
 **Preflight advises; it never blocks.** Report what you found and proceed
diff --git a/plugins/helm-framework/skills/helm-framework-migration/resources/values-contract.md b/plugins/helm-framework/skills/helm-framework-migration/resources/values-contract.md
index 2c12e6f..587eceb 100644
--- a/plugins/helm-framework/skills/helm-framework-migration/resources/values-contract.md
+++ b/plugins/helm-framework/skills/helm-framework-migration/resources/values-contract.md
@@ -1,4 +1,4 @@
-# helm-framework values contract (v1.0.0)
+# helm-framework values contract (v1.1.0)
 
 Generated from `helm/helm-framework/templates/` and `helm/helm-framework/values.yaml`.
 Do not edit by hand. This is what the migration playbook uses to classify a
diff --git a/plugins/helm-framework/skills/helm-framework/SKILL.md b/plugins/helm-framework/skills/helm-framework/SKILL.md
index 5e8c10f..7062e5f 100644
--- a/plugins/helm-framework/skills/helm-framework/SKILL.md
+++ b/plugins/helm-framework/skills/helm-framework/SKILL.md
@@ -21,7 +21,7 @@ point and configure everything through their own `values.yaml`.
 ```yaml
 dependencies:
   - name: helm-framework
-    version: "1.0.0"
+    version: "1.1.0"
     repository: "oci://ghcr.io/k8s-stuff"
 ```
 
@@ -30,7 +30,7 @@ dependencies:
 ```yaml
 dependencies:
   - name: helm-framework
-    version: "1.0.0"
+    version: "1.1.0"
     repository: "https://k8s-stuff.github.io/helm-framework"
 ```