@chronary/sdk 0.11.0 → 0.11.1

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,10 @@
2
2
 
3
3
  All notable changes to `@chronary/sdk` will be documented in this file starting with the soft-launch release.
4
4
 
5
+ ## 0.11.1 — 2026-11-16
6
+
7
+ - README: the plans table gains the Developer plan. Developer now has every paid-plan feature, scheduling proposals (1,000 a month) and temporal holds included (#2331). No code change.
8
+
5
9
  ## 0.11.0 — 2026-11-16
6
10
 
7
11
  - **Time-zone-aware recurrence (#2276).** `events.create()` takes `timezone` (IANA, e.g. `"America/Los_Angeles"`) and `events.update()` / `updateById()` take `timezone` (or `null` for UTC): a recurring series then repeats on local wall time across daylight-saving changes. Events gain `timezone`; expanded instances gain `startLocal`, `utcOffset` and `dstAdjusted` (`"gap"` when a DST gap moved the start forward).
package/README.md CHANGED
@@ -61,18 +61,22 @@ If `apiKey` is omitted, the SDK will also check `process.env.CHRONARY_API_KEY`.
61
61
 
62
62
  Chronary enforces a per-key rate limit and per-org monthly quotas that vary by plan:
63
63
 
64
- | | Free | Pro |
65
- |---|---|---|
66
- | Rate limit | 10 req/s | 50 req/s |
67
- | Webhook delivery retries | 4 | 8 |
68
- | Agents | 1 | 50 |
69
- | Calendars | 1 | 250 |
70
- | Events / mo | 100 | 125,000 |
71
- | API calls / mo | 1,000 | 1,000,000 |
72
- | Webhook deliveries / mo | 1,000 | 250,000 |
73
- | Pro-only features | — | Scheduling proposals, temporal holds, cross-calendar availability, per-agent API keys (`chr_ak_*`) |
74
-
75
- Pro-only feature calls return `403` with an upgrade hint on Free. See the full matrix and rate-limit handling guidance at <https://docs.chronary.ai/resources/rate-limits/>.
64
+ | | Free | Developer | Pro |
65
+ |---|---|---|---|
66
+ | Rate limit | 10 req/s | 25 req/s | 50 req/s |
67
+ | Webhook delivery retries | 4 | 6 | 8 |
68
+ | Agents | 1 | 10 | 50 |
69
+ | Calendars | 1 | 50 | 250 |
70
+ | Events / mo | 100 | 15,000 | 125,000 |
71
+ | API calls / mo | 1,000 | 200,000 | 1,000,000 |
72
+ | Webhook deliveries / mo | 1,000 | 25,000 | 250,000 |
73
+ | Scheduling proposals / mo | — | 1,000 | unlimited |
74
+ | Per-agent API keys (`chr_ak_*`) | — | 10 | 50 |
75
+ | Paid-plan features | — | all | all |
76
+
77
+ Paid-plan features are scheduling proposals, temporal holds, cross-agent availability, per-agent API keys, and webhook delivery replay and secret rotation. Developer and Pro have the same features and differ only in their limits.
78
+
79
+ Paid-plan feature calls return `403` with an upgrade hint on Free. See the full matrix and rate-limit handling guidance at <https://docs.chronary.ai/resources/rate-limits/>.
76
80
 
77
81
  ## Response headers and quota
78
82
 
package/dist/index.cjs CHANGED
@@ -46,7 +46,7 @@ __export(index_exports, {
46
46
  module.exports = __toCommonJS(index_exports);
47
47
 
48
48
  // src/version.ts
49
- var VERSION = "0.11.0";
49
+ var VERSION = "0.11.1";
50
50
 
51
51
  // src/error.ts
52
52
  function str(body, key) {
@@ -1321,6 +1321,10 @@ var WaitlistClient = class {
1321
1321
  * `tos_version` doesn't match the currently-published version.
1322
1322
  * @throws ChronaryError (429 `rate_limit_error`) on the per-IP / per-email
1323
1323
  * waitlist limiter.
1324
+ * @throws ChronaryError (400 `challenge_failed`) while the human check on the
1325
+ * console waitlist form is switched on (#2103). It applies only to that human
1326
+ * form, and an SDK client cannot solve it: an agent signs up with
1327
+ * `agentAuth.signUp` (`POST /v1/agent/sign-up`), which is never challenged.
1324
1328
  */
1325
1329
  join(params, options) {
1326
1330
  return this.client.request(