[krinart]

Adds an SDK Updates section to the v2.4.0 release blog, matching spiceai/spiceai#15678: spice.js v3.3.0, spicepy v4.0.1, spice-rs v5.0.0, spice-java v0.8.1, spice-dotnet v0.5.0, and gospice v9.1.0.

Adds an Agent Skills Updates section for spiceai/skills v2.4.0, matching spiceai/spiceai#15690.

[github-actions]

✅ Pull with Spice Passed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected
• ✅ Has at least one assignee: krinart

[Copilot]

🟡 Changes recommended

The release notes should limit automatic endpoint pairing to known local-runtime and Spice Cloud addresses and state that other self-hosted deployments must configure both URLs to avoid misdirected requests.

1 open issue

• Clarify endpoint pairing requirements for self-hosted deployments · New

What changed in this PR

This documentation-only PR adds SDK release information to the v2.4.0 release blog, covering client features, fixes, and upgrade requirements across all six SDKs.

Changes:

• Adds an SDK Updates section with links to each SDK release.
• Summarizes API additions, authentication fixes, parameter support, and compatibility changes.

File	Description
website/​releases/​v2.4.0.md	Documents updates for the JavaScript, Python, Rust, Java, .NET, and Go SDKs.

_{Review effort: Balanced}

[github-actions]

🚀 deployed to https://0386e2df.spiceai-org-website.pages.dev

[Copilot]

🔵 Needs a closer look

The endpoint-pairing claim omits its restriction to recognized Spice Cloud and local-runtime addresses, potentially causing users of other self-hosted runtimes to omit a required URL and send requests to the wrong runtime.

No open issues 🎉

1 resolved since last review

• Clarify endpoint pairing requirements for self-hosted deployments

_{Review effort: Balanced}

[github-actions]

🚀 deployed to https://879bab81.spiceai-org-website.pages.dev