Skip to content
AI Radar by Wagner Solution
CS
Menu
worth noting Coding

New SDK and CLI versions introduce breaking changes and the Apache 2.0 license

clearly official source

New versions of the SDK and CLI include breaking changes that are independent of the API version. They are also switching from MIT License to Apache 2.0.

New versions of the SDK and CLI include breaking changes that are independent of the API version. Keeping the same API version therefore does not, by itself, guarantee compatibility when updating these tools.

The new versions also use the Apache 2.0 license instead of the previous MIT License. See the source article for details.

What changed

Why it matters

Developers and teams must assess compatibility independently of the API version when updating an SDK or CLI. The license for the tools companies use is also changing, giving them a reason to check the terms for continued use.

Two audiences, two different impacts

What this means

01

For individuals

If you use an SDK or CLI, an update may require changes to your solution even if the API version stays the same.

What to do Before updating, review the changelog for the relevant SDK or CLI and check the compatibility of your solution.
More practical updates →
02

For a business

The switch to Apache 2.0 in new versions changes the licensing terms for tools the company uses in development.

Development
What to decide Before adopting the new version, check the terms of the Apache 2.0 license for your company's use case.
More business impacts →
Apache 2.0 Claude CLI MIT License SDK

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
Claude Platform Release Notes primary source · first detected The new SDK and CLI versions also have breaking changes that don't depend on the API version, and they are licensed under Apache 2.0 instead of the MIT License. See SDK and CLI…