@sunerpy/kiro-provider 3.3.1 → 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 +33 -0
- package/dist/cli.js +94 -86
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -78,6 +78,39 @@ For a service install, set `KIRO_PROVIDER_VERSION` to a release version instead
|
|
|
78
78
|
of following `latest`. See the [service guide](docs/SERVICE.md) for a pinned,
|
|
79
79
|
long-lived setup.
|
|
80
80
|
|
|
81
|
+
### Check the version and upgrade
|
|
82
|
+
|
|
83
|
+
`--version` prints the installed version only. Add `--check` to look up the
|
|
84
|
+
newest GitHub release, and `--json` for machine-readable output.
|
|
85
|
+
|
|
86
|
+
```bash
|
|
87
|
+
kiro-provider --version
|
|
88
|
+
kiro-provider --version --check
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
A standalone binary can replace itself. `self-update` downloads the release
|
|
92
|
+
asset for this platform, verifies it against the release's `SHA256SUMS`, and
|
|
93
|
+
only then swaps the binary in place; a digest mismatch leaves the installed
|
|
94
|
+
copy untouched.
|
|
95
|
+
|
|
96
|
+
```bash
|
|
97
|
+
kiro-provider self-update --check # report what would be installed
|
|
98
|
+
kiro-provider self-update # ask, then replace
|
|
99
|
+
kiro-provider self-update --yes # non-interactive
|
|
100
|
+
kiro-provider self-update --tag 3.3.1 # pin a release, including a downgrade
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
npm installs are upgraded with the package manager instead
|
|
104
|
+
(`bun add -g @sunerpy/kiro-provider@latest`); `self-update` refuses them and
|
|
105
|
+
says so. Both commands accept `--proxy <url>` and otherwise honour
|
|
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.
|
|
113
|
+
|
|
81
114
|
## Quickstart
|
|
82
115
|
|
|
83
116
|
### 1. Create the gateway config
|