@calimero-network/registry-cli 1.27.2 → 1.27.3
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 +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Command-line access to the Calimero App Registry: organizations, bundle metadata, and a local registry for development.
|
|
4
4
|
|
|
5
|
-
> **Building and publishing bundles is not this tool's job.** Use [`
|
|
5
|
+
> **Building and publishing bundles is not this tool's job.** Use core's [`meroctl`](https://github.com/calimero-network/core): `meroctl app pack` to build and sign, `meroctl app publish` to upload. See [PUBLISHING.md](../../PUBLISHING.md).
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
@@ -34,7 +34,7 @@ calimero-registry config reset [--force]
|
|
|
34
34
|
| `registry-url` | `CALIMERO_REGISTRY_URL` | `https://apps.calimero.network` |
|
|
35
35
|
| `api-key` | `CALIMERO_API_KEY` | none |
|
|
36
36
|
|
|
37
|
-
`registry-url` and `api-key` are the only keys. Get a token from the registry's Organizations page, under **CLI Access
|
|
37
|
+
`registry-url` and `api-key` are the only keys. Get a token from the registry's Organizations page, under **CLI Access**. `meroctl app publish` takes the same token but reads it from `CALIMERO_REGISTRY_API_KEY`, not `CALIMERO_API_KEY`; both read `CALIMERO_REGISTRY_URL`.
|
|
38
38
|
|
|
39
39
|
## Organizations
|
|
40
40
|
|
|
@@ -56,7 +56,7 @@ calimero-registry org packages link <orgId> <package>
|
|
|
56
56
|
calimero-registry org packages unlink <orgId> <package>
|
|
57
57
|
```
|
|
58
58
|
|
|
59
|
-
Members are identified by email, so removing someone takes effect on their next request with no key rotation involved. Linking a package to an org lets
|
|
59
|
+
Members are identified by email, so removing someone takes effect on their next request with no key rotation involved. Linking a package to an org lets its **admins and owners** publish new versions signed with another key, through either push endpoint; a plain member still signs with the key that owns the package. See the [ownership rules](../../README.md#ownership-and-publishing-rights).
|
|
60
60
|
|
|
61
61
|
## Bundles
|
|
62
62
|
|
|
@@ -75,7 +75,7 @@ calimero-registry bundle get <package> <version> [--local]
|
|
|
75
75
|
# push a pre-built .mpk
|
|
76
76
|
calimero-registry bundle push <bundle-file> [--local | --remote]
|
|
77
77
|
|
|
78
|
-
# assemble a bundle from a bare wasm (predates
|
|
78
|
+
# assemble a bundle from a bare wasm (predates meroctl app pack)
|
|
79
79
|
calimero-registry bundle create <wasm-file> [package] [version] \
|
|
80
80
|
[-o <path>] [--name <name>] [--description <text>] [--author <author>] \
|
|
81
81
|
[--frontend <url>] [--github <url>] [--docs <url>] [--abi <path>]
|
|
@@ -86,12 +86,12 @@ calimero-registry bundle create <wasm-file> [package] [version] \
|
|
|
86
86
|
```bash
|
|
87
87
|
calimero-registry bundle edit com.example.my-app 1.2.4 --remote \
|
|
88
88
|
--name "New Name" -o manifest.json # 1. fetch with changes applied
|
|
89
|
-
|
|
89
|
+
meroctl app sign manifest.json --key my-key.json # 2. sign
|
|
90
90
|
calimero-registry bundle edit com.example.my-app 1.2.4 --remote \
|
|
91
91
|
--manifest manifest.json # 3. PATCH back
|
|
92
92
|
```
|
|
93
93
|
|
|
94
|
-
`bundle create` and `bundle push` predate `
|
|
94
|
+
`bundle create` and `bundle push` predate `meroctl` and know nothing about compute components, frontends, pipelines, or icons. Use them only for a bundle built outside the Rust toolchain; anything built from a Calimero app crate should go through `meroctl app pack` and `meroctl app publish`.
|
|
95
95
|
|
|
96
96
|
## Local registry
|
|
97
97
|
|
package/package.json
CHANGED