pi-zengate-models 1.0.2 → 1.0.4

package/CHANGELOG.md

@@ -7,10 +7,10 @@
   A machine the gateway sync already prepared needs no second copy, and the
   session warning stops for those machines.
 - Name all three sources in that warning.
-- Pin the install lines to `1.0.2`.
 
 ## [Unreleased]
 
+- Install without a version tag, so `pi update --extensions` follows releases.
 - Add `scripts/setup.ps1` and `scripts/setup.sh`. They ask for the gateway URL
   and key, write `<agent-dir>/zengate.json` without a BOM, and move a stale
   `models.json` that holds only the static provider.

package/README.md

@@ -22,18 +22,19 @@ This package ships no endpoint and no key. Each machine supplies both.
 ## Install
 
 ```bash
-pi install npm:pi-zengate-models@1.0.2
+pi install npm:pi-zengate-models
 ```
 
 From git, or from a local checkout:
 
 ```bash
-pi install git:github.com/ham-zax/pi-zengate@v1.0.2
+pi install git:github.com/ham-zax/pi-zengate
 pi install /path/to/pi-zengate
 ```
 
-Pin the npm version. An older `0.0.0-stage` publish still holds the `latest` tag
-until it is removed, and that version has no extension.
+Install without a tag. A tag in the install command, such as `@v1.0.2`, freezes
+that machine on one version, and `pi update --extensions` then re-fetches the same
+tag forever. Without a tag, updates follow the newest release.
 
 ## Configure
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-zengate-models",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Pi provider extension that discovers free models and their metadata from an OpenAI-compatible gateway catalog, with a local cache and no scheduler.",
   "keywords": [
     "pi-package",