diff --git a/content/guides/api-calls/api-versioning-strategy.md b/content/guides/api-calls/api-versioning-strategy.md index 0975dd9a2..8543ea3e0 100644 --- a/content/guides/api-calls/api-versioning-strategy.md +++ b/content/guides/api-calls/api-versioning-strategy.md @@ -110,7 +110,7 @@ For details on possible errors, see [versioning errors](g://api-calls/permission ## How Box SDK versioning works -The versioning strategy applies only to [next generation generated SDKs](page://sdks-and-tools/#next-generation-sdks). +The versioning strategy applies only to [generated SDKs](page://sdks-and-tools/#next-generation-sdks). Box SDKs support the **All Versions In** SDK approach. This means that every release of SDK provides access to all endpoints in any version which is currently live. All generated SDKs use manager's approach - they group all endpoints with the same domain in one manager. diff --git a/content/guides/box-ai/index.md b/content/guides/box-ai/index.md index fb2f07935..aaac4820f 100644 --- a/content/guides/box-ai/index.md +++ b/content/guides/box-ai/index.md @@ -28,7 +28,7 @@ Box AI API provides a number of capabilities designed to help you leverage Large Language Models (LLMs) in your application workflows. -Currently, you can ask Box AI to answer +You can ask Box AI to answer user questions, summarize the document content, or generate text you can use in your documents. You can also use Box AI to extract metadata from the diff --git a/content/guides/tooling/sdks/dotnet-gen.md b/content/guides/tooling/sdks/dotnet-gen.md index b6ece6b30..1006939e4 100644 --- a/content/guides/tooling/sdks/dotnet-gen.md +++ b/content/guides/tooling/sdks/dotnet-gen.md @@ -15,13 +15,13 @@ alias_paths: [] Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate [branch][branch]. - - For more details, see our [SDK versioning strategy document][versioning]. + All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate [branch][sdk-branch]. -Check the [migration guide][migration] to learn how to switch from Box Next Generation SDK to Box core SDK `v10`. +Check the [migration guide][migration] to learn how to switch from the Box Next Generation SDK to the Box core SDK `v10`. + +For more details, see our [SDK versioning strategy document][versioning]. [versioning]: g://tooling/sdks/sdk-versioning -[branch]: https://github.com/box/box-windows-sdk-v2/tree/sdk-gen -[migration]: https://github.com/box/box-windows-sdk-v2/blob/sdk-gen/migration-guides/from-dotnet-sdk-gen-v1-to-box-windows-sdk-v10.md \ No newline at end of file +[sdk-branch]: https://github.com/box/box-windows-sdk-v2/tree/sdk-gen +[migration]: https://github.com/box/box-windows-sdk-v2/blob/sdk-gen/migration-guides/from-dotnet-sdk-gen-v1-to-box-windows-sdk.md \ No newline at end of file diff --git a/content/guides/tooling/sdks/index.md b/content/guides/tooling/sdks/index.md index 866b03629..ac55d748a 100644 --- a/content/guides/tooling/sdks/index.md +++ b/content/guides/tooling/sdks/index.md @@ -65,17 +65,18 @@ Refer to [this][android-docs] documentation for more details. In keeping with industry best practices, we are consolidating the Box Next Generation SDKs and Box core SDKs into a single package for each programming language. This makes migration efforts much easier and allows seamless additions of new capabilities to existing applications still powered by Box core SDKs, which were maintained manually. - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate branch. + **All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate branch.** For more details, see our [SDK versioning strategy document][versioning]. -The latest generation Box Python SDK, Box TypeScript -SDK, Box .NET SDK, and Box Swift SDK are designed to elevate the developer +`v10` of Python SDK, Box TypeScript +SDK, Box .NET SDK, Box Java SDK, and Box Swift SDK are designed +to elevate the developer experience and streamline your integration with Box Content Cloud. -Here's what you can expect from the new SDKs: +Here's what you can expect from `v10`: - **Full API support**: New Box SDKs empower developers with complete coverage of the Box API ecosystem. You can access all the latest features and functionalities offered by Box and build feature-rich applications. - **Rapid API updates**: The new auto-generation development approach allows you to add Box APIs to SDKs at a much faster pace (in a matter of days). This means you can leverage the most up-to-date features in your applications without delay. diff --git a/content/guides/tooling/sdks/java-gen.md b/content/guides/tooling/sdks/java-gen.md index 4844c76cf..244514ca3 100644 --- a/content/guides/tooling/sdks/java-gen.md +++ b/content/guides/tooling/sdks/java-gen.md @@ -15,13 +15,13 @@ alias_paths: [] Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate [branch][branch]. - - For more details, see our [SDK versioning strategy document][versioning]. + **All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate [branch][sdk-branch].** -Check the [migration guide][migration] to learn how to switch from Box Next Generation SDK to Box core SDK `v10`. +Check the [migration guide][migration] to learn how to switch from the Box Next Generation SDK to the Box core SDK `v10`. + +For more details, see our [SDK versioning strategy document][versioning]. [versioning]: g://tooling/sdks/sdk-versioning -[branch]: https://github.com/box/box-java-sdk/tree/sdk-gen -[migration]: https://github.com/box/box-java-sdk/blob/sdk-gen/migration-guides/from-box-java-sdk-gen-v0-to-box-java-sdk-v10.md \ No newline at end of file +[sdk-branch]: https://github.com/box/box-java-sdk/tree/sdk-gen +[migration]: https://github.com/box/box-java-sdk/blob/sdk-gen/migration-guides/from-box-java-sdk-gen-v0-to-box-java-sdk.md \ No newline at end of file diff --git a/content/guides/tooling/sdks/python-gen.md b/content/guides/tooling/sdks/python-gen.md index a2f1f751b..8a0b67326 100644 --- a/content/guides/tooling/sdks/python-gen.md +++ b/content/guides/tooling/sdks/python-gen.md @@ -14,13 +14,14 @@ alias_paths: [] As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts. Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. - - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate branch. - For more details, see our [SDK versioning strategy document][versioning]. + **All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate [branch][sdk-branch].** -Check the [migration guide][migration] to learn how to switch from Box Next Generation SDK to Box core SDK `v10`. +Check the [migration guide][migration] to learn how to switch from the Box Next Generation SDK to the Box core SDK `v10`. + +For more details, see our [SDK versioning strategy document][versioning]. [versioning]: g://tooling/sdks/sdk-versioning -[migration]: https://github.com/box/box-python-sdk/blob/sdk-gen/migration-guides/from-box-python-sdk-gen-v1-to-box-python-sdk-v10.md \ No newline at end of file +[migration]: https://github.com/box/box-python-sdk/blob/sdk-gen/migration-guides/from-box-python-sdk-gen-v1-to-box-python-sdk.md +[sdk-branch]: https://github.com/box/box-python-sdk/tree/sdk-gen \ No newline at end of file diff --git a/content/guides/tooling/sdks/sdk-versioning.md b/content/guides/tooling/sdks/sdk-versioning.md index 39a1f1598..1d1fb743a 100644 --- a/content/guides/tooling/sdks/sdk-versioning.md +++ b/content/guides/tooling/sdks/sdk-versioning.md @@ -13,63 +13,109 @@ alias_paths: [] # Box SDK versioning strategy -As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts. +The Box core SDKs and the Box Next Generation SDKs were initially created as separate libraries. However, in keeping with industry best practices, **we are consolidating the Box Next Generation SDKs and the Box core SDKs into a single package for each programming language**. This makes migration efforts much easier and allows seamless addition of new capabilities to existing applications still powered by older versions of the Box core SDKs, which were maintained manually. -Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. +To facilitate this migration process, there are two actively maintained major Box core SDK versions: -## Why we are making this change +- **A major version that follows sequential versioning for each SDK artifact and includes:** the manually maintained package and the generated one. This SDK version enables leveraging coexisting packages at the same time, and serves as a transition phase. Support for the consolidated version of each Box core SDKs will continue in 2027. +- `v10` that includes **only the generated package**. -In keeping with industry best practices, we are consolidating the Box Next Generation SDKs and Box core SDKs into a single package for each programming language. This makes migration efforts much easier and allows seamless addition of new capabilities to existing applications still powered by Box core SDKs, which were maintained manually. +Here's what you can expect from generated packages of the Box SDK: -All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate branch. +- **Full API support**: New Box SDKs empower developers with complete coverage of the Box API ecosystem. You can access all the latest features and functionalities offered by Box and build feature-rich applications. +- **Rapid API updates**: The new auto-generation development approach allows you to add Box APIs to SDKs at a much faster pace (in a matter of days). This means you can leverage the most up-to-date features in your applications without delay. +- **Embedded documentation**: All objects and parameters are documented directly in the source code of the SDK so all the necessary information is stored in one place. +- **Enhanced convenience methods**: The newly introduced convenience methods cover various aspects such as authentication, chunk uploads, exponential back-offs, automatic retries, type checkers that help to ensure that you’re using variables correctly, and much more. -## How it will work +## What it means for your project -Box core SDKs and Box Next Generation SDKs were created as separate libraries. Going forward, the Box core SDK artifacts will include: + + + If you have an existing application that relies on the Box core SDK and you wish to further develop your project: -- `(n+1)` major version will include manually maintained **Box core SDK** and **Box Next Generation SDK** artifacts. This version enables leveraging coexisting artifacts at the same time, and serve as a transition phase. Stay tuned for this upcoming release. -- `v10.0.0` version includes **only the Box Next Generation SDK artifact**. Currently, this version is available as a branch for each SDK repository. + **Action** Use the major version that includes consolidated packages. Start using convenience methods and new features from the generated package, and gradually migrate your codebase. Ultimately, migrate to the Box core SDK package (≥`v10.0.0`). + + + If you have an existing application that relies only on the Box Next Generation SDK and you wish to further develop your project: -## How to decide + **Action** Replace the library name in your package manager with the Box core SDK package (≥`v10.0.0`). Check migration guides for detailed instructions. + + + If you have an existing application that relies both on the Box core SDK and the Next Generation SDK: -1. If you are creating a new application, use `v10` of the Box core SDK package. -2. If you have an existing application relying on the **Box Next Generation SDK** and you wish to further develop your project, replace the name of this library in the package manager with the Box core SDK package (`v10.0.0`). Object imports for most SDKs will persist the same and your code will work as-is; the TypeScript SDK requires additional steps for migrating. Check the section below for detailed guides. -3. If you have an existing application relying on **Box core SDK** and you wish to further develop your project, once released, bump the library version by one major release. See the table above for a detailed breakdown of recommended versions. -4. If you have an existing application that you don’t plan to change, ensure your package manager includes the version of SDK you are using to prevent an accidental rebuild that pulls in a version you aren’t expecting. + **Action** Use the major version that includes consolidated packages. Ultimately, migrate to the Box core SDK package (≥`v10.0.0`). + + + If you are creating a new application: + + **Action** Use ≥`v10.0.0` of the Box core SDK. + + + If you have an existing application that you don't plan to change: + + **Action** Ensure your package manager includes the specific version to prevent accidental updates. We strongly recommend upgrading to the major version, which includes consolidated packages, to receive ongoing security patches and improvements. + + ## Versioning overview -### Box SDK versions and artifacts +### Box core SDK versions and artifacts overview + +| Repository name | Artifact name | Includes both packages | Includes generated package only | +|--------------|------|---------|----------| +| [`box-python-sdk`][python-repo] | `boxsdk` | [`v4.X.Y`][python-combined] | [`≥v10.0.0`][python-v10] | +| [`box-node-sdk`][node-repo] | `box-node-sdk` | [`v4.X.Y`][node-combined] | [`≥v10.0.0`][node-v10] | +| [`box-java-sdk`][java-repo] | `box-java-sdk` | [`v5.X.Y`][java-combined] | [`≥v10.0.0`][java-v10] | +| [`box-windows-sdk-v2`][windows-repo] | `Box.V2`, `Box.V2.Core` | [`v6.X.Y`][windows-combined] | [`≥v10.0.0`][windows-v10] | +| [`box-ios-sdk`][ios-repo] | `BoxSDK` | [`v6.X.Y`][ios-combined] | [`≥v10.0.0`][ios-v10] | + +## Box Next Gen SDKs deprecation + +As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts. Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. + +**All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate branch.** + +| Repository name | Artifact name | Note | +|------|---------------|--------| +|`box-python-sdk-gen` | `box-sdk-gen` | Deprecated, use `boxsdk` [`≥v10.0.0`][python-v10] | +| `box-typescript-sdk-gen` | `box-typescript-sdk-gen` | Deprecated, use `box-node-sdk` [`≥v10.0.0`][node-v10] | +| `box-java-sdk-gen` | `box-java-sdk-gen` | Deprecated, use `box-java-sdk` [`≥v10.0.0`][java-v10] | +| `box-dotnet-sdk-gen` | `Box.Sdk.Gen` | Deprecated, use `Box.V2.Core` [`≥v10.0.0`][windows-v10] | +| `box-swift-sdk-gen` | `BoxSdkGen` | Deprecated, use `BoxSDK` [`≥v10.0.0`][ios-v10] | + +## Migration + +### Migration from manually maintained SDK version to the consolidated SDK version + +Follow detailed migration guides to migrate from the manually maintained SDK version to the consolidated SDK version: + +- [Python `v3` to `v4`][python-migration-v4] +- [Node `v3` to `v4`][node-migration-v4] +- [Java `v4` to `v5`][java-migration-v5] +- [.NET `v5` to `v6`][windows-migration-v6] +- [Swift `v5` to `v6`][ios-migration-v6] -| Repository name | Artifact name | Current latest version | Will include both SDK artifacts | Includes only Box Next Gen SDK artifact | -|--------------|------|---------|----------|----------| -| [`box-python-sdk`][python-repo] | `boxsdk` | `v3.14.0` | `v4.X.Y` | >=`v10.0.0` | -| [`box-node-sdk`][node-repo] | `box-node-sdk` |`v3.8.2` | `v4.X.Y` | >=`v10.0.0` | -| [`box-java-sdk`][java-repo] | `box-java-sdk` | `v4.16.3` | `v5.X.Y`| >=`v10.0.0` | -| [`box-windows-sdk-v2`][windows-repo] | `Box.V2`, `Box.V2.Core` | `v5.8.0` | `v6.X.Y`| >=`v10.0.0` | -| [`box-ios-sdk`][ios-repo] | `BoxSDK` | `v5.6.0` | `v6.X.Y`| >=`v10.0.0` | +Once your project is upgraded, follow the migration guides and migrate to the generated package. -### Box Next Gen SDK deprecation status +### Migration to the generated package -| Repository name | Artifact name | Current latest version | Note | -|------|---------------|-------------------------|-------| -|`box-python-sdk-gen` | `box-sdk-gen` | `v1.17.0` | Deprecated, use `boxsdk` >=[`v10.0.0`][python-v10] | -| `box-typescript-sdk-gen` | `box-typescript-sdk-gen` | `v1.19.1` | Deprecated, use `box-node-sdk` >=[`v10.0.0`][node-v10] | -| `box-java-sdk-gen` | `box-java-sdk-gen` |`v0.8.1` | Deprecated, use `box-java-sdk` >=[`v10.0.0`][java-v10] | -| `box-dotnet-sdk-gen` | `Box.Sdk.Gen` | `v1.12.0` | Deprecated, use `Box.V2.Core` >=[`v10.0.0`][windows-v10] | -| `box-swift-sdk-gen` | `BoxSdkGen` | `v0.6.3` | Deprecated, use `BoxSDK` >=[`v10.0.0`][ios-v10] | +Follow detailed migration guides to migrate to the generated package within the Box core SDKs. -## Migration +- [Python: migrate from `boxsdk` to `box_sdk_gen` package][python-migration-gen] +- [Node: migrate from `box-node-sdk` to `sdk-gen`][node-migration-gen] +- [Java: migrate migrate from `com.box.sdk` to com.`box.sdkgen` package][java-migration-gen] +- [.NET: migrate from `Box.V2` module to `Box.Sdk.Gen` module][windows-migration-gen] +- [Swift: migrate from `BoxSDK` module to `BoxSdkGe`n module][swift-migration-gen] -### Migrating from Box Next Generations SDKs to core Box SDK `v10` +### Migration from the Box Next Generation SDKs to the Box core SDKs -Follow detailed migrations guides to migrate from from Box Next Generations SDKs to Box core SDK `v10`: +Follow detailed migration guides to migrate from the Box Next Generation SDKs to the Box core SDK ≥`v10`: -- [Python][python-migration] -- [TypeScript][ts-migration] -- [Java][java-migration] -- [.NET][dotnet-migration] -- [Swift][swift-migration] +- [Python][python-migration-next-gen] +- [TypeScript/Node][ts-migration-next-gen] +- [Java][java-migration-next-gen] +- [.NET][dotnet-migration-next-gen] +- [Swift][swift-migration-next-gen] [node-repo]: https://github.com/box/box-node-sdk [windows-repo]: https://github.com/box/box-windows-sdk-v2 @@ -79,12 +125,30 @@ Follow detailed migrations guides to migrate from from Box Next Generations SDKs [java-v10]: https://github.com/box/box-java-sdk/tree/sdk-gen [ios-v10]: https://github.com/box/box-ios-sdk/tree/sdk-gen -[node-v10]: https://github.com/box/box-windows-sdk-v2/tree/sdk-gen +[node-v10]: https://github.com/box/box-node-sdk/tree/sdk-gen [python-v10]: https://github.com/box/box-python-sdk/tree/sdk-gen [windows-v10]: https://github.com/box/box-windows-sdk-v2/tree/sdk-gen -[java-migration]: https://github.com/box/box-java-sdk/blob/sdk-gen/migration-guides/from-box-java-sdk-gen-v0-to-box-java-sdk-v10.md -[python-migration]: https://github.com/box/box-python-sdk/blob/sdk-gen/migration-guides/from-box-python-sdk-gen-v1-to-box-python-sdk-v10.md -[swift-migration]: https://github.com/box/box-ios-sdk/blob/sdk-gen/migration-guides/from-box-swift-sdk-gen-v0-to-box-ios-sdk-v10.md -[ts-migration]: https://github.com/box/box-node-sdk/blob/sdk-gen/docs/migration-guides/from-box-typescript-sdk-gen-v1-to-box-node-sdk-v10.md -[dotnet-migration]: https://github.com/box/box-windows-sdk-v2/blob/sdk-gen/migration-guides/from-dotnet-sdk-gen-v1-to-box-windows-sdk-v10.md \ No newline at end of file +[python-combined]: https://github.com/box/box-python-sdk/tree/combined-sdk +[java-combined]: https://github.com/box/box-java-sdk/tree/combined-sdk +[node-combined]: https://github.com/box/box-node-sdk/tree/combined-sdk +[ios-combined]: https://github.com/box/box-ios-sdk/tree/combined-sdk +[windows-combined]: https://github.com/box/box-windows-sdk-v2/tree/combined-sdk + +[python-migration-v4]: https://github.com/box/box-python-sdk/blob/combined-sdk/migration-guides/from-v3-to-v4.md +[node-migration-v4]: https://github.com/box/box-node-sdk/blob/combined-sdk/migration-guides/from-v3-to-v4.md +[ios-migration-v6]: https://github.com/box/box-ios-sdk/blob/combined-sdk/migration-guides/from-v5-to-v6.md +[windows-migration-v6]: https://github.com/box/box-windows-sdk-v2/blob/combined-sdk/migration-guides/from-v5-to-v6.md +[java-migration-v5]: https://github.com/box/box-java-sdk/blob/combined-sdk/migration-guides/from-v4-to-v5.md + +[java-migration-next-gen]: https://github.com/box/box-java-sdk/blob/combined-sdk/migration-guides/from-box-java-sdk-gen-v0-to-box-java-sdk.md +[python-migration-next-gen]: https://github.com/box/box-python-sdk/blob/combined-sdk/migration-guides/from-box-python-sdk-gen-v1-to-box-python-sdk.md +[swift-migration-next-gen]: https://github.com/box/box-ios-sdk/blob/combined-sdk/migration-guides/from-box-swift-sdk-gen-v0-to-box-ios-sdk.md +[ts-migration-next-gen]: https://github.com/box/box-node-sdk/blob/combined-sdk/migration-guides/from-box-typescript-sdk-gen-v1-to-box-node-sdk.md +[dotnet-migration-next-gen]: https://github.com/box/box-windows-sdk-v2/blob/combined-sdk/migration-guides/from-dotnet-sdk-gen-v1-to-box-windows-sdk.md + +[python-migration-gen]: https://github.com/box/box-python-sdk/blob/combined-sdk/migration-guides/from-boxsdk-to-box_sdk_gen.md +[windows-migration-gen]: https://github.com/box/box-windows-sdk-v2/blob/combined-sdk/migration-guides/from-box-v2-to-box-sdk-gen-namespace.md +[swift-migration-gen]: https://github.com/box/box-ios-sdk/blob/combined-sdk/migration-guides/from-BoxSDK-to-BoxSdkGen.md +[java-migration-gen]: https://github.com/box/box-java-sdk/blob/combined-sdk/migration-guides/from-com-box-sdk-to-com-box-sdkgen.md +[node-migration-gen]: https://github.com/box/box-node-sdk/blob/combined-sdk/migration-guides/from-box-node-sdk-to-sdk-gen.md \ No newline at end of file diff --git a/content/guides/tooling/sdks/swift-gen.md b/content/guides/tooling/sdks/swift-gen.md index a9322d7dc..e2f8d12d2 100644 --- a/content/guides/tooling/sdks/swift-gen.md +++ b/content/guides/tooling/sdks/swift-gen.md @@ -16,12 +16,13 @@ alias_paths: [] Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate branch. - - For more details, see our [SDK versioning strategy document][versioning]. + **All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate [branch][sdk-branch].** -Check the [migration guide][migration] to learn how to switch from Box Next Generation SDK to Box core SDK `v10`. +Check the [migration guide][migration] to learn how to switch from the Box Next Generation SDK to the Box core SDK `v10`. + +For more details, see our [SDK versioning strategy document][versioning]. [versioning]: g://tooling/sdks/sdk-versioning -[migration]: https://github.com/box/box-ios-sdk/blob/sdk-gen/migration-guides/from-box-swift-sdk-gen-v0-to-box-ios-sdk-v10.md \ No newline at end of file +[migration]: https://github.com/box/box-ios-sdk/blob/sdk-gen/migration-guides/from-box-swift-sdk-gen-v0-to-box-ios-sdk.md +[sdk-branch]: https://github.com/box/box-ios-sdk/tree/sdk-gen \ No newline at end of file diff --git a/content/guides/tooling/sdks/typescript-gen.md b/content/guides/tooling/sdks/typescript-gen.md index d800a7906..baa09193c 100644 --- a/content/guides/tooling/sdks/typescript-gen.md +++ b/content/guides/tooling/sdks/typescript-gen.md @@ -15,12 +15,13 @@ alias_paths: [] Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate branch. - - For more details, see our [SDK versioning strategy document][versioning]. + **All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate [branch][sdk-branch].** -Check the [migration guide][migration] to learn how to switch from Box Next Generation SDK to Box core SDK `v10`. +Check the [migration guide][migration] to learn how to switch from the Box Next Generation SDK to the Box core SDK `v10`. + +For more details, see our [SDK versioning strategy document][versioning]. [versioning]: g://tooling/sdks/sdk-versioning -[migration]: https://github.com/box/box-node-sdk/blob/sdk-gen/docs/migration-guides/from-box-typescript-sdk-gen-v1-to-box-node-sdk-v10.md \ No newline at end of file +[migration]: https://github.com/box/box-node-sdk/blob/sdk-gen/docs/migration-guides/from-box-typescript-sdk-gen-v1-to-box-node-sdk.md +[sdk-branch]: https://github.com/box/box-node-sdk/tree/sdk-gen diff --git a/content/microcopy/reference.yml b/content/microcopy/reference.yml index 7a4e47945..1ba7a9389 100644 --- a/content/microcopy/reference.yml +++ b/content/microcopy/reference.yml @@ -165,19 +165,19 @@ environments: // node: |- A label for Node JS code sample - DO NOT TRANSLATE - node: Node v3 + node: Node v4 // dotnet: |- A label for .NET code sample - DO NOT TRANSLATE - dotnet: .NET v5 + dotnet: .NET v6 // java: |- A label for Java code sample - DO NOT TRANSLATE - java: Java v4 + java: Java v5 // python: |- A label for Python code sample - DO NOT TRANSLATE - python: Python v3 + python: Python v4 // cli: |- A label for command line interface code sample - DO NOT TRANSLATE @@ -188,7 +188,7 @@ environments: curl: cURL // ios: |- A label for iOS code sample - DO NOT TRANSLATE - ios: iOS v5 + ios: iOS v6 // ts_gen: |- A label for TypeScript code sample from auto-generated SDK - DO NOT TRANSLATE diff --git a/content/pages/sdks-and-tools/index.md b/content/pages/sdks-and-tools/index.md index 4bbc647dd..1c42a0e0c 100644 --- a/content/pages/sdks-and-tools/index.md +++ b/content/pages/sdks-and-tools/index.md @@ -69,12 +69,12 @@ Refer to [this][android-docs] documentation for more details. Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes. - All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version `v10`. Currently, `v10` is available as a separate branch. + **All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version `v10` of the Box core SDKs, and it is currently available as a separate branch.** For more details, see our [SDK versioning strategy document][versioning]. -Here's what you can expect from generated SDKs: +Here's what you can expect from `v10`: - **Full API support**: New Box SDKs empower developers with complete coverage of the Box API ecosystem. You can access all the latest features and functionalities offered by Box and build feature-rich applications. - **Rapid API updates**: The new auto-generation development approach allows you to add Box APIs to SDKs at a much faster pace (in a matter of days). This means you can leverage the most up-to-date features in your applications without delay.