Skip to content

v2.7.1

Choose a tag to compare

@jeffyaw jeffyaw released this 11 Nov 14:21
· 7 commits to main since this release
v2.7.1
90a251f

Changed

  • A tools/call whose undeclared arguments total more than 64 KiB is refused with JSON-RPC -32602 instead of being processed with those arguments silently dropped. Undeclared arguments are never read by any tool, so no legitimate input is lost: declared arguments are never measured, and large ones (an aws_lambda_invoke payload, aws_call params, aws_script code, an aws_resource_* desired state) go through as before. A small stray argument is still ignored. The refusal names the undeclared keys (at most 10, each cut to 64 characters) and the tool's declared ones. This clears the security-oversized-input warning from @yawlabs/mcp-compliance on both the Node and oam legs.

Fixed

  • A client cancel now stops the aws CLI child already in flight, instead of leaving it to run to its per-call timeout (60s by default). runAwsCall takes an AbortSignal: already aborted, nothing is spawned; aborted mid-call, the child is killed through the same path the timeout uses and the call settles at once as cancelled. Wired into aws_sso_list_assignments / aws_sso_generate_profiles discovery, aws_multi_region and aws_multi_account, where an in-flight entry now comes back as errorKind: "cancelled".
  • Concurrent writes to ~/.aws/credentials or the AWS config file no longer fail spuriously on Windows. Under contention, Windows can fail the exclusive create of <file>.lock with EPERM/EACCES instead of EEXIST (likely a lock file whose delete is still pending), and the writer treated that as fatal, so a concurrent aws_assume_role or aws_sso_generate_profiles could fail with EPERM ... credentials.lock. On Windows an unbroken run of those errors is now retried as contention for up to 1 s, after which the real error is reported, so a genuinely read-only ~/.aws still fails fast with its true cause. Other platforms are unchanged.