Announced long-term support plan for Composable Commerce SDKs
We have set up a long-term support plan to actively support and maintain Version 1 SDKs until their end of life. Additionally, we have provided information about migration to our Version 2 SDKs that are constantly updated with the newest API features as soon as they are released. This support plan indicates when you could schedule the migration to Version 2 SDKs.
Active Support: The SDK will be actively maintained and upgraded with new functionalities and improvements made to existing functionalities. We will fix the reported bugs and provide patches for security vulnerabilities.
Maintenance Support: The SDK is nearing end of life and will only receive features, bug fixes, and security patches for a short time. We will add the functionality only if customers explicitly request it via support tickets or GitHub issues.
End of life: The SDK is no longer maintained and will not be patched to fix bugs or security vulnerabilities.
|SDK||Active Support||Maintenance Support||End of Life|
|JVM SDK Version 1*||28 February 2022||31 December 2023||1 January 2024|
|PHP SDK Version 1||28 February 2022||31 August 2022||1 September 2022|
|DotNET Core SDK Version 1||28 February 2022||31 August 2022||1 September 2022|
|DotNET SDK||not provided||not provided||1 September 2021|
* Maintenance Support and End of Life for the JVM SDK Version 1 was extended. These dates were previously 31 December 2022 and 1 January 2023 respectively.
What does this mean for you?
You don't need to take any action as long as the SDK is in Active Support. We recommend migrating to the respective Version 2 SDK before the Version 1 SDK reaches End of Life. If needed, you can still request enhancements to the Version 1 SDK until the end of its Maintenance Support.
Why is this changing?
Our Version 1 SDKs have served a long term, but it requires a lot of effort to keep them up-to-date with new API feature releases. Our Version 2 SDKs are auto-generated from the API specification, keeping them in sync with API features as and when they are released. This reduces the amount of time you, as SDK users, have to wait until you can utilize a new API feature.
Which SDKs should you migrate to?
You should migrate to these auto-generated SDKs:
Are there any guides on migrating to new SDKs?
Yes, the above-mentioned SDK documentation pages provide links to their respective migration guides.