pi-cliproxyapi-provider 0.2.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/data/models-dev-fallback.json +1 -1
- package/package.json +1 -1
- package/src/model-capabilities.ts +54 -0
- package/src/provider.ts +13 -1
- package/src/types.ts +3 -0
package/README.md
CHANGED
|
@@ -146,7 +146,7 @@ Startup registers the provider immediately from the last-known-good local snapsh
|
|
|
146
146
|
|
|
147
147
|
Manual refreshes update the running provider immediately; `/reload` is not required. Failed refreshes retain the last-known-good data independently for each source.
|
|
148
148
|
|
|
149
|
-
A scheduled GitHub Actions workflow checks the bundled fallback catalog daily. When it changes, the workflow validates the package, bumps the patch version, commits the update, and
|
|
149
|
+
A scheduled GitHub Actions workflow checks the bundled fallback catalog daily. When it changes, the workflow validates the package, bumps the patch version, commits the update, and starts the normal release workflow. Maintainers can also update the catalog locally with:
|
|
150
150
|
|
|
151
151
|
```bash
|
|
152
152
|
npm run update:models-dev
|
|
@@ -160,4 +160,4 @@ npm test
|
|
|
160
160
|
|
|
161
161
|
## Release
|
|
162
162
|
|
|
163
|
-
|
|
163
|
+
Changing the `package.json` version on `master` automatically creates a matching Git tag and GitHub Release, generates release notes, and publishes the package to npm. Changed daily models.dev catalogs also produce automatic patch releases through the same workflow. See [RELEASING.md](RELEASING.md) for authentication, versioning, verification, and troubleshooting.
|