Learn more about our deprecation process by reviewing our Developer Terms. urgent security/infrastructural reasons), we may need to move faster (or in some cases for major changes, slower) than the given timeline. Scripting extensionĢ weeks Private Beta We will determine the deprecation timeline for private beta features on a case-by-case basis. It is not a requirement to pre-announce new major versions. a change to the blocks model bridge that affects all custom apps independent of SDK version, or a change to our minimum supported SDK version). This timeline requirement is for changes independent of versioning (e.g. *Note: Unlike other areas, both the Blocks SDK and CLI are versioned, and breaking changes are only released as part of major versions. While we will do our best to meet the timeframes below, we reserve the right to deprecate any API without notice. We will include this period of time in our announcement for each specific deprecation or breaking change. In addition, when changing behavior, our goal will be to support both the old and new behaviors simultaneously for a period of time before completely removing the old API. Where possible, we will provide a gradual rollout and migration path rather than a direct removal or breaking change. ![]() We aim to give developers time to migrate over to the new API. For example, the planned removal of a Web API endpoint or a helper function from the Blocks SDK is considered a deprecation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |