@arbol-ai/cli 1.20261018.213455 → 1.20261019.5745

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.
Files changed (3) hide show
  1. package/README.md +17 -23
  2. package/dist/index.js +47964 -34938
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -12,16 +12,9 @@ npm install --global @arbol-ai/cli
12
12
  arbol --version
13
13
  ```
14
14
 
15
- It needs Node.js 26 or newer, whose `fetch` and `Temporal` the SDK uses. On macOS and Linux,
16
- [cli.getarbol.com](https://cli.getarbol.com) does the same in one line:
17
-
18
- ```sh
19
- curl -fsSL https://cli.getarbol.com/install.sh | sh
20
- ```
21
-
22
- [`install.sh`](site/public/install.sh) checks for Node.js 26 and runs
23
- `npm install --global @arbol-ai/cli`, or prints that command when npm is missing. Run it again to
24
- update; `ARBOL_VERSION=<version>` installs a given release.
15
+ It needs Node.js 26 or newer, whose `fetch` and `Temporal` the SDK uses. The same command updates it.
16
+ An `arbol` installed before the CLI was on npm comes first or blocks the install: remove it with
17
+ `npm uninstall --global @getarbol/cli`, or delete `~/.local/bin/arbol` and `~/.local/share/arbol`.
25
18
 
26
19
  ## Profiles
27
20
 
@@ -162,19 +155,20 @@ A release of the API flows through three repositories, each started by the one b
162
155
  `openapi-release` to project-arbol-sdk-js.
163
156
  2. **project-arbol-sdk-js** regenerates `@arbol-ai/sdk` from it, publishes it to npm and sends
164
157
  `sdk-release` (`{ "version": "<release>" }`) here.
165
- 3. **Here**, [Generate](.github/workflows/generate.yml) pins `@arbol-ai/sdk` to exactly that release,
166
- regenerates `src/generated/` from the live OpenAPI and, when anything changed and `bun run verify`
167
- passes, commits `Release <release>` to main and runs [Publish](.github/workflows/publish.yml) on that
168
- commit. When nothing changed, nothing is committed or published.
169
-
170
- Generate also runs every 6 hours and by hand, pinning the SDK release the OpenAPI names once it is on
171
- npm. Its push uses an installation token of the organization's GitHub App (Arbol Bot: the variable
172
- `ARBOL_BOT_APP_ID` and the secret `ARBOL_BOT_PRIVATE_KEY`), so the commit runs Verify like any other.
173
- Publish can also run by hand, for a change to the CLI alone; npm receives the package with the
174
- organization's `NPM_TOKEN` and a provenance statement.
175
-
176
- [cli.getarbol.com](https://cli.getarbol.com) is the Worker in [`site/`](site/wrangler.jsonc): static
177
- files and no code. Cloudflare Workers Builds deploys it on every push to main that changes `site/`.
158
+ 3. **Here**, [Generate](.github/workflows/generate.yml) releases only when the OpenAPI's content
159
+ changed: the SHA-256 of its canonical JSON without `info.version` (keys sorted, no whitespace; see
160
+ [`generation/openapi-hash.ts`](generation/openapi-hash.ts), the same hash sdk-js computes), compared
161
+ with `openapiContentSha256` in main's `src/generated/generation.json`. When it is equal, the run
162
+ stops and nothing is committed or published. Otherwise Generate pins `@arbol-ai/sdk` to exactly the
163
+ release sdk-js named, regenerates `src/generated/`, and when `bun run verify` passes commits
164
+ `Release <release>` to main and runs [Publish](.github/workflows/publish.yml) on that commit.
165
+
166
+ Generate also runs every 6 hours and by hand, with the same hash check, pinning the SDK release the
167
+ OpenAPI names once it is on npm. Its push uses an installation token of the organization's GitHub App
168
+ (Arbol Bot: the variable `ARBOL_BOT_APP_ID` and the secret `ARBOL_BOT_PRIVATE_KEY`), so the commit runs
169
+ Verify like any other. A change to the CLI's own code, which the OpenAPI does not carry, is released by
170
+ running Publish by hand on main. npm receives the package with the organization's `NPM_TOKEN` and a
171
+ provenance statement.
178
172
 
179
173
  ## License
180
174