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

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