From 133ca23635e7cfb5ceb9e71f1856d24bd9669c69 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 4 Aug 2026 03:03:42 +0000 Subject: [PATCH] chore: release packages --- .changeset/brave-moons-repeat.md | 9 --------- .changeset/shaggy-taxis-shout.md | 7 ------- packages/cli/CHANGELOG.md | 13 +++++++++++++ packages/cli/lib/config.js | 2 +- packages/cli/package.json | 2 +- packages/core/CHANGELOG.md | 8 ++++++++ packages/core/package.json | 2 +- 7 files changed, 24 insertions(+), 19 deletions(-) delete mode 100644 .changeset/brave-moons-repeat.md delete mode 100644 .changeset/shaggy-taxis-shout.md diff --git a/.changeset/brave-moons-repeat.md b/.changeset/brave-moons-repeat.md deleted file mode 100644 index 038ca7c..0000000 --- a/.changeset/brave-moons-repeat.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@call-e/cli": patch ---- - -Reject duration flags that are not plain numbers, and bound the ones backed by a timer. - -`--timeout-seconds 30s` used to resolve to `NaN`, which reached the MCP timeout arithmetic where `Math.max(NaN, 1000)` stays `NaN` and `setTimeout` substitutes 1ms, so every call aborted before it left. Durations are now validated where they are read, with the offending flag named in the error. - -The constraints are per option rather than shared: `--min-ttl-seconds 0` keeps working, since zero disables the minimum remaining-lifetime window, while the timeout flags stay strictly positive. Timer-backed values are also capped at 2147483 seconds, because `setTimeout` collapses any longer delay to 1ms and would reproduce the same immediate abort. diff --git a/.changeset/shaggy-taxis-shout.md b/.changeset/shaggy-taxis-shout.md deleted file mode 100644 index ef89046..0000000 --- a/.changeset/shaggy-taxis-shout.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@call-e/core": patch ---- - -Guard the MCP request timeout against a non-numeric duration. - -`Math.max(NaN, 1000)` is `NaN`, and `setTimeout(fn, NaN)` fires after 1ms, so an unreadable timeout aborted every request immediately instead of falling back to a usable one. diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index c0a4d54..59a56e9 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,18 @@ # @call-e/cli +## 0.3.9 + +### Patch Changes + +- [#73](https://github.com/CALLE-AI/call-e-integrations/pull/73) [`89a5237`](https://github.com/CALLE-AI/call-e-integrations/commit/89a5237f9b0a8d82a79752c4f09dde2a8c9f9ba9) Thanks [@EazyHood](https://github.com/EazyHood)! - Reject duration flags that are not plain numbers, and bound the ones backed by a timer. + + `--timeout-seconds 30s` used to resolve to `NaN`, which reached the MCP timeout arithmetic where `Math.max(NaN, 1000)` stays `NaN` and `setTimeout` substitutes 1ms, so every call aborted before it left. Durations are now validated where they are read, with the offending flag named in the error. + + The constraints are per option rather than shared: `--min-ttl-seconds 0` keeps working, since zero disables the minimum remaining-lifetime window, while the timeout flags stay strictly positive. Timer-backed values are also capped at 2147483 seconds, because `setTimeout` collapses any longer delay to 1ms and would reproduce the same immediate abort. + +- Updated dependencies [[`89a5237`](https://github.com/CALLE-AI/call-e-integrations/commit/89a5237f9b0a8d82a79752c4f09dde2a8c9f9ba9)]: + - @call-e/core@0.2.5 + ## 0.3.8 ### Patch Changes diff --git a/packages/cli/lib/config.js b/packages/cli/lib/config.js index 216ca77..8783739 100644 --- a/packages/cli/lib/config.js +++ b/packages/cli/lib/config.js @@ -39,7 +39,7 @@ export const DEFAULT_SERVER_NAME = "calle"; export const DEFAULT_POLL_TIMEOUT_SECONDS = 300; export const DEFAULT_TELEMETRY_TIMEOUT_SECONDS = 1.5; export const DEFAULT_CACHE_ROOT = path.join(os.homedir(), ".calle-mcp", "cli"); -export const CLI_VERSION = "0.3.8"; +export const CLI_VERSION = "0.3.9"; function firstOptionValue(value) { return Array.isArray(value) ? value[0] : value; diff --git a/packages/cli/package.json b/packages/cli/package.json index 83f15b8..f2ca2db 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@call-e/cli", - "version": "0.3.8", + "version": "0.3.9", "description": "CLI wrapper for brokered MCP login and CALL-E MCP client configuration.", "type": "module", "license": "MIT", diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md index 162ee4e..34d4dd8 100644 --- a/packages/core/CHANGELOG.md +++ b/packages/core/CHANGELOG.md @@ -1,5 +1,13 @@ # @call-e/core +## 0.2.5 + +### Patch Changes + +- [#73](https://github.com/CALLE-AI/call-e-integrations/pull/73) [`89a5237`](https://github.com/CALLE-AI/call-e-integrations/commit/89a5237f9b0a8d82a79752c4f09dde2a8c9f9ba9) Thanks [@EazyHood](https://github.com/EazyHood)! - Guard the MCP request timeout against a non-numeric duration. + + `Math.max(NaN, 1000)` is `NaN`, and `setTimeout(fn, NaN)` fires after 1ms, so an unreadable timeout aborted every request immediately instead of falling back to a usable one. + ## 0.2.4 ### Patch Changes diff --git a/packages/core/package.json b/packages/core/package.json index 876c6b8..3050dcf 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "name": "@call-e/core", - "version": "0.2.4", + "version": "0.2.5", "description": "Shared CALL-E runtime helpers for brokered auth, local token cache, and MCP HTTP calls.", "type": "module", "types": "./lib/index.d.ts",