chore(omz-pnpm-plugin): default to v1.1.0, a mirror of upstream

Upstream ntnyq/omz-plugin-pnpm merged the PNPM_HOME fix (rewritten, with
tests; the plugin no longer calls pnpm on shell start). Upstream publishes
no tags, so the itplusx fork now serves as tag source: v1.1.0 points at
upstream main a5c3b08. Bump the feature to 1.0.1 with that default ref.

Author: vacijj

README.md

@@ -16,7 +16,7 @@ Custom [Dev Container Features](https://containers.dev/implementors/features/) m
 ```json
 "features": {
     "ghcr.io/itplusx/devcontainer-features/shared-pnpm-store:1.1.0": {},
-    "ghcr.io/itplusx/devcontainer-features/omz-pnpm-plugin:1.0.0": {}
+    "ghcr.io/itplusx/devcontainer-features/omz-pnpm-plugin:1.0.1": {}
 }
 ```
 

src/omz-pnpm-plugin/NOTES.md

@@ -14,18 +14,20 @@
 ## Why a fork
 
 The original [ntnyq/omz-plugin-pnpm](https://github.com/ntnyq/omz-plugin-pnpm)
-is unmaintained and mishandles `PNPM_HOME`:
+used to mishandle `PNPM_HOME`:
 
-- when `pnpm -g bin` fails (fresh container, bin dir not on `PATH`) it still
-  runs `export PNPM_HOME=""`, and pnpm treats an empty `PNPM_HOME` as the
-  current directory. Every pnpm call then creates `global/` and
+- when `pnpm -g bin` failed (fresh container, bin dir not on `PATH`) it still
+  ran `export PNPM_HOME=""`, and pnpm treats an empty `PNPM_HOME` as the
+  current directory. Every pnpm call then created `global/` and
   `package-manager-store/` in your project root.
-- when `pnpm -g bin` succeeds it overrides `PNPM_HOME` with the bin dir. On
+- when `pnpm -g bin` succeeded it overrode `PNPM_HOME` with the bin dir. On
   pnpm 11+ that is `$PNPM_HOME/bin`, which moves the package-manager store out
   of the volume that [`shared-pnpm-store`](../shared-pnpm-store) mounts.
 
-The fork leaves a pre-set `PNPM_HOME` alone and never exports an empty one.
-Aliases are unchanged.
+Both are fixed upstream since September 2026 (the plugin no longer calls pnpm
+on shell start at all). Upstream publishes no tags, so the fork exists as a
+tag source: `v1.0.0` is the original itplusx fix, `v1.1.0` and later mirror
+upstream commits verbatim. Aliases are unchanged either way.
 
 ## Pairing with `shared-pnpm-store`
 
@@ -39,7 +41,7 @@ does not undo that.
         "plugins": "git docker"
     },
     "ghcr.io/itplusx/devcontainer-features/shared-pnpm-store:1.1.0": {},
-    "ghcr.io/itplusx/devcontainer-features/omz-pnpm-plugin:1.0.0": {}
+    "ghcr.io/itplusx/devcontainer-features/omz-pnpm-plugin:1.0.1": {}
 }
 ```
 
@@ -60,4 +62,5 @@ source). Without oh-my-zsh the feature installs cleanly and does nothing.
 
 | Version | Notes           |
 | ------- | --------------- |
+| 1.0.1   | Default `ref` is `v1.1.0`, a mirror of upstream after the `PNPM_HOME` fix landed there |
 | 1.0.0   | Initial release |

src/omz-pnpm-plugin/devcontainer-feature.json

@@ -1,14 +1,15 @@
 {
     "name": "oh-my-zsh pnpm plugin",
     "id": "omz-pnpm-plugin",
-    "version": "1.0.0",
+    "version": "1.0.1",
     "documentationURL": "https://github.com/itplusx/devcontainer-features/tree/main/src/omz-pnpm-plugin",
-    "description": "Installs the itplusx fork of the omz-plugin-pnpm oh-my-zsh plugin (pnpm aliases) into the remote user's oh-my-zsh custom plugins and activates it. The fork respects a pre-set PNPM_HOME and never exports an empty one.",
+    "description": "Installs the omz-plugin-pnpm oh-my-zsh plugin (pnpm aliases) from the itplusx tag mirror into the remote user's oh-my-zsh custom plugins and activates it. The plugin respects a pre-set PNPM_HOME and never leaves it empty.",
     "options": {
         "ref": {
             "type": "string",
-            "default": "v1.0.0",
+            "default": "v1.1.0",
             "proposals": [
+                "v1.1.0",
                 "v1.0.0",
                 "main"
             ],

src/omz-pnpm-plugin/install.sh

@@ -2,7 +2,7 @@
 
 set -euo pipefail
 
-REF="${REF:-v1.0.0}"
+REF="${REF:-v1.1.0}"
 ACTIVATE="${ACTIVATE:-true}"
 USERNAME=${USERNAME:-${_REMOTE_USER:-}}
 USER_HOME=${_REMOTE_USER_HOME:-}