Deprecation Schedule
REST API
REST APIs can be found in our API Reference and are prefixed by a version number. This version number is the major version number for the API. Any time SGP releases breaking changes, they will be grouped together into a new major version upgrade. Any past APIs that are replaced will then be placed on a deprecation schedule. That schedule is shown below. Any minor version upgrades or patches will be done in-place under the latest API version.
API Version | Actively Supported? | Support End Date | Discontinuation Date |
---|---|---|---|
/v4 | Yes | ||
/v3 | No | April 1, 2024 | |
/v2 | No | March 1, 2024 | |
/v1 | No | February 1, 2024 | February 10, 2024 |
Python SDK
Our Python SDK can be found on PyPI under the package named scale-egp. This SDK follows SemVer versioning semantics which adheres to the following rules:
Given a version number MAJOR.MINOR.PATCH
, increment the:
- MAJOR version when you make incompatible API changes
- MINOR version when you add functionality in a backward compatible manner
- PATCH version when you make backward compatible bug fixes
Each version of the SDK can continue to be used until the REST API version that the SDK release depends on is exceeds its discontinuation date. That and any previous version of the SDK will then also be marked as discontinued. That schedule for support is shown below.
SDK Version | Actively Supported? | Support Ended | Discontinuation Date |
---|---|---|---|
1.X.X | Yes | ||
0.X.X | No | March 5, 2024 |
Updated 4 months ago