@reminix/cli 1.0.0-rc.7 → 1.0.0-rc.9

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/CHANGELOG.md +179 -0
  2. package/dist/reminix.mjs +1228 -664
  3. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -2,6 +2,185 @@
2
2
 
3
3
  What changed in the Reminix CLI (`@reminix/cli`). Generated from the source on each release; newest first.
4
4
 
5
+ ## 1.0.0-rc.9 (2026-11-07)
6
+
7
+ ### Added
8
+
9
+ - Lists can start from a date. `GET /v1/workspace/audit-events` and
10
+ `GET /v1/workspace/webhook-endpoints/{endpointId}/deliveries` take
11
+ `before`, an ISO time, and return the items older than it, newest first.
12
+
13
+ Audit events take two filters. `action` keeps one kind of event.
14
+ `actor` keeps what one person, key or token did: pass `user:` and an
15
+ item's `actor.id`, or `credential:` and its `credential.id`. Each audit
16
+ event now carries those ids.
17
+
18
+ Webhook deliveries take `status`: `pending`, `delivered` or `failed`.
19
+ - Listing runs takes `status`, which keeps only runs in one state, such as
20
+ `failed`. Listing runs and listing files both take `before`, which starts
21
+ the list from a moment instead of from now. For example,
22
+ `before=2026-11-01T00:00:00Z` lists what came before November.
23
+
24
+ ### Changed
25
+
26
+ - The usage count `authors` is now described as "People who published or
27
+ uploaded this month". Its id and numbers haven't changed.
28
+ - Listing files filters by file name with `name`, which replaces `q`. Every
29
+ filter is now named after the field it narrows.
30
+
31
+ ## 1.0.0-rc.8 (2026-11-07)
32
+
33
+ ### Added
34
+
35
+ - `reminix files download <file-id> --json` prints the file's details and
36
+ where it was saved, like every other command's `--json`.
37
+ - A `run.cancelled` webhook event, sent when a run is cancelled: by
38
+ someone (`runs.cancel`), or because its approval was denied, expired or
39
+ couldn't start. Its `data` is the same as `run.failed`'s, with `error`
40
+ saying why. Triggers can start a script on it.
41
+ - Each plan now limits how many runs a workspace has going at once: 1 on
42
+ Free, 5 on Pro and 15 on Business, short and long runs together. Of
43
+ those, at most 2 can be long runs on Pro and 5 on Business. Starting
44
+ one more answers `429 rate_limited` with a `Retry-After` header (a few
45
+ seconds for a short run, 30 for a long one) instead of running; the
46
+ SDKs and the CLI wait and try again on their own.
47
+ - You can now change a webhook endpoint's URL, description or event types
48
+ without deleting it: `client.workspace.webhookEndpoints.update()`
49
+ (`PATCH /v1/workspace/webhook-endpoints/{endpointId}`). The endpoint
50
+ keeps its signing secret, so your verification code keeps working.
51
+
52
+ ### Changed
53
+
54
+ - An AI agent connected through the MCP server can no longer change who
55
+ may run a script or which of its runs need approval:
56
+ `PATCH /v1/scripts/{slug}` (`scripts.update`) answers `403 forbidden`
57
+ when an agent's token sends `access`, `teamIds` or `approvalPolicy`.
58
+ People's own tokens and API keys change them as before. And with
59
+ `approvalPolicy: "always"`, an agent's run now always waits for
60
+ approval, even when an owner or admin connected the agent.
61
+ - An approval request (`POST /v1/workspace/approval-requests`) now runs in
62
+ the environment it was filed in once a person approves it, such as live
63
+ when you asked from live. Before, it ran in the default environment
64
+ unless its input named one. Requests filed before this change still
65
+ run in the default.
66
+ - The descriptions of every method and command are rewritten to be easier
67
+ to read: one rule per sentence, with nothing about how calls behave
68
+ changed. They now also say that only workspace owners can manage webhook
69
+ endpoints with a personal access token.
70
+ Every response in the API reference now comes with an example of what
71
+ it returns.
72
+ - Error messages and CLI output read as whole sentences: what went wrong,
73
+ then what to do. For example, an unknown environment now says
74
+ `Unknown environment "staging". This product's environments are test, live.`
75
+ Error codes are unchanged, so code that checks `error.code` keeps
76
+ working. Code that matches the exact text of a message may need
77
+ updating.
78
+ - One name per idea, across the API, the SDKs, the CLI and MCP (breaking,
79
+ before 1.0):
80
+
81
+ - Upload a version is `scriptVersions.upload` (`script_versions.upload`
82
+ in Python), and takes `source` (was `archive`), `install` (was
83
+ `build`), `timeoutSeconds` (was `timeout`) and `envVars` (was `env`).
84
+ A version answers with `version` (was `number`), `install`,
85
+ `installLog`, `buildBytes`, `buildSha256`, `envVars` and `via` (was
86
+ `createdVia`); version paths are `/versions/{version}`.
87
+ - Test-run a version is `scriptVersions.testRun` (`test_run`).
88
+ - A run has `via` (was `interface`; an agent's runs are `agent`, was
89
+ `mcp`) and `startedBy: { userId, name, credential: { type, name } }`.
90
+ Its log is `runs.log` at `GET /v1/runs/{runId}/log` (was `runs.logs`,
91
+ `/logs`). The 202 schema is `RunAwaitingApproval` (was `HeldRun`).
92
+ - A file has `origin` (`input` or `saved`, was `direction` `in`/`out`),
93
+ `input` (was `field`) and `mediaType` (was `type`); list files with
94
+ `?origin=`. `files.upload` and `files.download` (at
95
+ `GET /v1/files/{fileId}/download`) replace `files.create` and
96
+ `files.content`. The SDKs' `FileUpload` takes `mediaType`
97
+ (`media_type` in Python). A script saves files to `/saved`
98
+ (`$REMINIX_SAVED`, was `/outputs`), and reads its inputs file at
99
+ `$REMINIX_INPUTS_FILE` (was `$REMINIX_INPUTS`).
100
+ - Secrets: `allowEnvVar` (was `allowEnv`; the CLI's `--allow-env-var`),
101
+ a secret use's `format` (was `value`), and `secretValues.delete`
102
+ (`reminix secret-values delete`, was `secrets.unset`).
103
+ - Triggers have `lastRunAt` (was `lastFiredAt`); a script's
104
+ `usedBy.startsScripts` was `followedBy`; an environment's `usedBy` was
105
+ `usage`. The event `run.succeeded` was `run.completed`. Script ids
106
+ start `scr_`.
107
+ - The CLI: `reminix upload [dir...]` uploads a draft (`publish --draft`
108
+ is gone), and `--dry-run` replaces `--plan`.
109
+ - Path parameters such as `endpointId` and `deliveryId` now come with a
110
+ description ("The endpoint's ID.") in the SDKs' type hints, the
111
+ command line's help and the API reference.
112
+ - `login` and `logout` now point to **Account → Personal access tokens**,
113
+ the page's new name in the app (it was "API tokens").
114
+ - The API reference's "Too many requests" answer now gives the limit: 100
115
+ requests a minute for each credential, whether an API key, a personal
116
+ access token or an agent's sign-in. Wait the number of seconds in the
117
+ `Retry-After` header before trying again.
118
+ - Method and command descriptions are clearer, and say who can call each
119
+ one. A workspace API key's access to updating, archiving, restoring and
120
+ test-running scripts is now stated. The CLI's `reminix publish`,
121
+ `reminix upload` and `reminix run` shortcuts describe themselves the
122
+ same way as the full commands.
123
+ - Error messages are easier to read. Each one states the problem in one
124
+ sentence, then what to do in the next:
125
+
126
+ ```text
127
+ SHOP_KEY has no value in staging. Add it in Settings → Scripts.
128
+ ```
129
+
130
+ If your code matches the text of an error, match its `code` instead.
131
+ The codes haven't changed.
132
+ - Environments and secrets now live under **Settings → Scripts** in the
133
+ app. A run error that sends you to the app to fix a secret or an
134
+ environment now names that tab.
135
+ - A run's `output`, `error` and log (`GET /v1/runs/{id}`,
136
+ `GET /v1/runs/{id}/log`) never show a secret value the run had access
137
+ to: printed as it is, or base64- or URL-encoded, it reads `[secret]`.
138
+ - API keys and webhooks now live together under **Settings → Developers**
139
+ in the app, and the descriptions of the API key and webhook endpoint
140
+ operations point there.
141
+ - `POST /v1/scripts/{slug}/runs` no longer fails a run because no machine
142
+ was free at once: the run waits up to 2 minutes for one, and its
143
+ `timeoutSeconds` counts from when its code starts. A short run still
144
+ answers `200` when it ends within 60 seconds; one still going then
145
+ answers `202` with status `running`, like a long run, and you follow it
146
+ with `GET /v1/runs/{id}`.
147
+ - `GET /v1/workspace/usage` returns its list as `counts` instead of `meters`.
148
+ Update anything that reads `meters` from `client.workspace.usage.get()`, the
149
+ Python client or the CLI's output.
150
+
151
+ ### Fixed
152
+
153
+ - `files.upload` refuses a file over the plan's size with `402
154
+ plan_limit_reached`, naming the plan's limit, on every plan. On Pro and
155
+ Business a file just over 100 MB used to get a generic `413` instead.
156
+ - Clearer, corrected descriptions for Reminix's operations in the API
157
+ reference, the SDKs' type hints, the command line's help and the MCP
158
+ tools:
159
+
160
+ - `runs.create` (and `scriptVersions.testRun`) documents its 429: 100
161
+ requests a minute per key or token, or the plan's runs at once all
162
+ going. Its 402 now also names used-up long-run minutes and a file
163
+ input larger than the plan takes, and its 400 an archived script. A
164
+ run takes at most its version's `timeoutSeconds`, not always 30.
165
+ - `runs.cancel` says a cancelled run sends a `run.cancelled` event, and
166
+ that a workspace API key may cancel too.
167
+ - `files.upload` documents its 413: uploads over 1,000 MB are refused.
168
+ An upload can be given to one run.
169
+ - `files.get`: an upload not yet used is also readable by owners,
170
+ admins and workspace API keys.
171
+ - `scripts.update`: its 402 is about every-run approval (Business), and
172
+ it changes tags too. `scriptSettings.update`: its 402 is about
173
+ second-person publishing (Business).
174
+ - `schedules.update` and `triggers.update`: `enabled` no longer claims a
175
+ default; leaving it out keeps it as it is.
176
+ - Name rules are given where they are checked: a script's `slug`, its
177
+ tags, an environment's `name`, a secret's `name`, and a secret's
178
+ `value` (at most 16,384 bytes).
179
+ - A run that waited for approval now reports when it actually started:
180
+ its `startedAt` (`GET /v1/runs/{id}`, and a run wherever the SDKs and
181
+ the CLI show one) is when it was approved, not when it was requested, and a cancelled long run's
182
+ `durationMs` counts only the time it ran, never the wait.
183
+
5
184
  ## 1.0.0-rc.7 (2026-10-19)
6
185
 
7
186
  ### Changed