@sunerpy/kiro-provider 3.4.0 → 3.4.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 +7 -3
- package/dist/cli.js +61 -61
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -103,9 +103,13 @@ kiro-provider self-update --tag 3.3.1 # pin a release, including a downgrad
|
|
|
103
103
|
npm installs are upgraded with the package manager instead
|
|
104
104
|
(`bun add -g @sunerpy/kiro-provider@latest`); `self-update` refuses them and
|
|
105
105
|
says so. Both commands accept `--proxy <url>` and otherwise honour
|
|
106
|
-
`KIRO_PROVIDER_PROXY_URL`, then `HTTPS_PROXY`/`HTTP_PROXY
|
|
107
|
-
|
|
108
|
-
|
|
106
|
+
`KIRO_PROVIDER_PROXY_URL`, then `HTTPS_PROXY`/`HTTP_PROXY`; `--proxy ""` selects
|
|
107
|
+
no proxy instead of falling through to those variables. Bun's `fetch` reads
|
|
108
|
+
`HTTPS_PROXY`/`HTTP_PROXY` itself, so unset them for a fully direct connection.
|
|
109
|
+
Replacing the binary needs write access to the install directory, not to the
|
|
110
|
+
binary itself, so a hardened read-only install still updates. Neither command
|
|
111
|
+
loads the gateway config, so a broken `config.json` cannot block an upgrade.
|
|
112
|
+
Restart the service after updating a service install.
|
|
109
113
|
|
|
110
114
|
## Quickstart
|
|
111
115
|
|