chore: release packages - #76
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@call-e/cli@0.3.9
Patch Changes
#73
89a5237Thanks @EazyHood! - Reject duration flags that are not plain numbers, and bound the ones backed by a timer.--timeout-seconds 30sused to resolve toNaN, which reached the MCP timeout arithmetic whereMath.max(NaN, 1000)staysNaNandsetTimeoutsubstitutes 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 0keeps 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, becausesetTimeoutcollapses any longer delay to 1ms and would reproduce the same immediate abort.Updated dependencies [
89a5237]:@call-e/core@0.2.5
Patch Changes
#73
89a5237Thanks @EazyHood! - Guard the MCP request timeout against a non-numeric duration.Math.max(NaN, 1000)isNaN, andsetTimeout(fn, NaN)fires after 1ms, so an unreadable timeout aborted every request immediately instead of falling back to a usable one.