<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sdk on Kuldeep Pisda</title><link>https://kdpisda.in/tag/sdk/</link><description>Recent content in Sdk on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 Oct 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/sdk/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrading the Anthropic SDK Now Changes Your API Version, Your Auth Header, and Whether temperature Works</title><link>https://kdpisda.in/anthropic-api-2026-10-21-sdk-bump-changes-wire-contract/</link><pubDate>Sat, 24 Oct 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/anthropic-api-2026-10-21-sdk-bump-changes-wire-contract/</guid><description>&lt;p&gt;If your Anthropic integration goes through an official SDK, you have never had to think about the &lt;code&gt;anthropic-version&lt;/code&gt; header. The SDK sent it for you. That convenience is now the risk: the migration guide for API version &lt;code&gt;2026-10-21&lt;/code&gt; says an SDK uses the API version that was current when its major version was released, and the new majors (Python 2.0.0, TypeScript 1.0.0, Go 2.0.0, Java 3.0.0, Ruby 2.0.0, PHP 1.0.0, C# 13.0.0, &lt;code&gt;ant&lt;/code&gt; CLI 2.0.0) all send &lt;code&gt;2026-10-21&lt;/code&gt;. A dependency bump is therefore also a server-side contract change, and the two failures that matter most look very different: one is a loud 400, the other is a header that your own infrastructure silently stops seeing.&lt;/p&gt;</description></item></channel></rss>