@limitry/cli 1.0.0-rc.11 → 1.0.0-rc.13

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/CHANGELOG.md CHANGED
@@ -2,6 +2,90 @@
2
2
 
3
3
  What changed in the Limitry CLI (`@limitry/cli`). Generated from the source on each release; newest first.
4
4
 
5
+ ## 1.0.0-rc.13 (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
+
20
+ ### Changed
21
+
22
+ - `limitry.limits.credits.list()` and `limitry limits credits list` now page
23
+ like every other list (`GET /v1/limits/{limitId}/credits`). They return
24
+ one page of credits and a `nextCursor`, and take `limit`, `cursor` and
25
+ `before`. `subjectId` keeps one subject's credits. The list no longer
26
+ stops at the newest 200.
27
+
28
+ ## 1.0.0-rc.12 (2026-11-07)
29
+
30
+ ### Added
31
+
32
+ - `limitry limits sync` (and `limitry sync`) also takes the whole request
33
+ as `--data '{"limits": [ … ]}'`, as every other command does, instead of
34
+ a file. `--preview` and `--archive-missing` still apply on top.
35
+
36
+ ### Changed
37
+
38
+ - An approval request (`POST /v1/workspace/approval-requests`) now runs in
39
+ the environment it was filed in once a person approves it, such as live
40
+ when you asked from live. Before, it ran in the default environment
41
+ unless its input named one. Requests filed before this change still
42
+ run in the default.
43
+ - The descriptions of every method and command are rewritten to be easier
44
+ to read: one rule per sentence, with nothing about how calls behave
45
+ changed. They now also say that only workspace owners can manage webhook
46
+ endpoints with a personal access token.
47
+ Every response in the API reference now comes with an example of what
48
+ it returns.
49
+ - The descriptions of the limits, subjects, checks, reservations and usage
50
+ methods are rewritten in plain sentences, with nothing about how calls
51
+ behave changed. Every field these methods return now has an example in
52
+ the API reference.
53
+ - A few error messages now read as separate sentences: what went wrong,
54
+ then what to do. Their codes and status are unchanged.
55
+ - Error messages and CLI output read as whole sentences: what went wrong,
56
+ then what to do. For example, an unknown environment now says
57
+ `Unknown environment "staging". This product's environments are test, live.`
58
+ Error codes are unchanged, so code that checks `error.code` keeps
59
+ working. Code that matches the exact text of a message may need
60
+ updating.
61
+ - Path parameters such as `endpointId` and `deliveryId` now come with a
62
+ description ("The endpoint's ID.") in the SDKs' type hints, the
63
+ command line's help and the API reference.
64
+ - The API reference's "Too many requests" answer now gives the limit: 100
65
+ requests a minute for each credential, whether an API key, a personal
66
+ access token or an agent's sign-in. Wait the number of seconds in the
67
+ `Retry-After` header before trying again.
68
+ - `POST /v1/checks` now caps refused checks per API key. Past about 17 refused
69
+ checks a second in one location, repeating a check that was just refused gets
70
+ the same `allowed: false` answer for up to 5 seconds, with the header
71
+ `limitry-refusal: repeated`. Past about 100 a second, the key's checks answer
72
+ `429 rate_limited` for 10 seconds, and each limit's fail mode decides. Allowed
73
+ checks, commits, releases and extends aren't affected.
74
+ - API keys and webhooks now live together under **Settings → Developers**
75
+ in the app, and the descriptions of the API key and webhook endpoint
76
+ operations point there.
77
+ - `GET /v1/workspace/usage` returns its list as `counts` instead of `meters`.
78
+ Update anything that reads `meters` from `client.workspace.usage.get()`, the
79
+ Python client or the CLI's output.
80
+
81
+ ### Fixed
82
+
83
+ - The API's descriptions, shown in the SDKs' hints and the CLI's help, now
84
+ state the real limits: `GET /v1/usage/subjects` returns at most 50
85
+ subjects (25 for a concurrent limit), a usage series spans at most 2,000
86
+ buckets, a check's idempotency answer lasts an hour, a late commit still
87
+ counts within 24 hours, and a test key's checks have no plan grace.
88
+
5
89
  ## 1.0.0-rc.11 (2026-10-27)
6
90
 
7
91
  ### Added
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  The Limitry CLI sets up your limits and checks them from a terminal, a script or an agent: create a limit, try a check, and see who is using what, in test before live.
4
4
 
5
- Limitry is the limits, credits and budgets layer for your software: give each of your users, teams, tenants, API keys or agents an allowance, and before any costly action one call tells your code whether it may happen.
5
+ Limitry is the limits, credits and budgets layer for the software you build: give each of your users, teams, tenants, API keys or agents an allowance, and before any costly action one call tells your code whether it may happen.
6
6
 
7
7
  ## Install
8
8