SDK consolidated version release

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.

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

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].
 </Message>
 
-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
+[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

content/guides/tooling/sdks/index.md

@@ -65,17 +65,17 @@ 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].
 </Message>
 
-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, and Box Swift SDK is 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.

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].**
 </Message>
 
-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
+[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

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].**
 </Message>
 
-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
+[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