Skip to content

Commit 0921dfa

Browse files
SowaProgramujeSowaProgramuje
committed
Update SDK messaging
1 parent 5ced392 commit 0921dfa

7 files changed

Lines changed: 67 additions & 66 deletions

File tree

‎content/guides/tooling/sdks/dotnet-gen.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,21 +14,21 @@ alias_paths: []
1414
# Deprecated .NET SDK
1515

1616
<Message type='warning'>
17-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. **Don’t worry, your existing code will continue to work without changes**.
17+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
1818

19-
To learn more visit our SDK [versioning strategy document][versioning]
20-
</Message>
19+
Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
20+
21+
All future development, including new features and updates for Next Generation SDKs, will now be delivered through Box core SDKs starting with version `v10`.
22+
23+
For more details, see our [SDK versioning strategy document][versioning].
24+
</Message
2125

2226
You can use Box .NET SDK to call Box APIs in a .NET
2327
project.
2428

2529
The SDK is available for both .NET Framework 4.5 and .NET Core 1.0 or
2630
above. The installation of the SDK depends on the framework used.
2731

28-
<CTA to="https://github.com/box/box-dotnet-sdk-gen">
29-
Learn more about .NET SDK on GitHub
30-
</CTA>
31-
3232
To install the .NET SDK in the .NET framework, run the following command using
3333
the [Nuget][nuget] package manager.
3434

@@ -37,4 +37,4 @@ PM> Install-Package Box.Sdk.Gen
3737
```
3838

3939
[nuget]: https://www.nuget.org/
40-
[versioning]: g://tooling/sdks/sdk-versioning
40+
[versioning]: g://tooling/sdks/sdk-versioning

‎content/guides/tooling/sdks/index.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ alias_paths:
1010
- /docs/community-supported-projects
1111
---
1212

13-
# SDKs
13+
# Box SDKs
1414

1515
Box offers a set of SDKs
1616
you can use to build your application.
@@ -30,7 +30,7 @@ with partial API parity lack some functionality while we work on bringing
3030
these projects to full parity.
3131
</Message>
3232

33-
The table lists legacy Box SDKs that you can use when building your
33+
The table lists Box SDKs that you can use when building your
3434
applications. For latest API support and features, use the next
3535
generation SDKs.
3636

@@ -56,18 +56,18 @@ build apps on Android.
5656
Refer to [this][android-docs] documentation for more details.
5757
</Message>
5858

59-
## Next generation SDKs
59+
## Next Generation SDKs
6060

6161
<Message type='warning'>
62-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. **Don’t worry, your existing code will continue to work without changes**.
62+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
6363

64-
## Why we are making this change
64+
Don't worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
6565

66-
In keeping with industry best practices, we are consolidating the Next Gen and legacy SDKs into a single package. This makes migration efforts much easier and allows you to seamlessly add new capabilities to existing applications still powered by the legacy SDKs.
66+
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 to seamlessly add new capabilities to existing applications still powered by the manually maintained Box core SDKs.
6767

68-
Ultimately, the Next Generation SDKs will replace the current legacy SDKs as the latest major version release.
68+
Box Next Generation SDKs are now available as the latest major version release (`v10`) of Box core SDKs.
6969

70-
To learn more visit our SDK [versioning strategy document][versioning]
70+
For more details, see our [SDK versioning strategy document][versioning].
7171
</Message>
7272

7373
The latest generation Box Python SDK, Box TypeScript

‎content/guides/tooling/sdks/python-gen.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,13 @@ alias_paths: []
1414
# Deprecated Python SDK
1515

1616
<Message type='warning'>
17-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. **Don’t worry, your existing code will continue to work without changes**.
17+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
1818

19-
To learn more visit our SDK [versioning strategy document][versioning]
19+
Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
20+
21+
All future development, including new features and updates for Next Generation SDKs, will now be delivered through Box core SDKs starting with version `v10`.
22+
23+
For more details, see our [SDK versioning strategy document][versioning].
2024
</Message>
2125

2226
You can use the **auto-generated** Box Python SDK to call Box APIs in a Python project.

‎content/guides/tooling/sdks/sdk-versioning.md‎

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -13,48 +13,48 @@ alias_paths: []
1313

1414
# Box SDK versioning strategy
1515

16-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. Don’t worry, your existing code will continue to work without changes.
16+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
17+
18+
Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
1719

1820
## Why we are making this change
1921

20-
In keeping with industry best practices, we are consolidating the Next Gen and legacy SDKs into a single package. This makes migration efforts much easier and allows you to seamlessly add new capabilities to existing applications still powered by the legacy SDKs.
22+
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.
2123

22-
Ultimately, the Next Generation SDKs will replace the current legacy SDKs as the latest major version release.
24+
All future development, including new features and updates for Next Generation SDKs, will now be delivered through Box core SDKs starting with version `v10`.
2325

2426
## How it will work
2527

26-
Currently, the legacy SDKs and the Next Gen SDKs are separate libraries. Going forward, two new major versions will be available within the legacy SDK artifact:
28+
Box core SDKs and Box Next Generation SDKs were created as separate libraries. Going forward, within the Box core SDK artifacts will include:
2729

28-
- `(n+1)` major version that includes legacy SDK and Next Gen SDK artifacts. This version enables you to leverage coexisting artifacts at the same time, and serve as a transition phase.
29-
- `v10.0.0` version that includes only the Next Gen SDK artifact.
30+
- `(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.
31+
- `v10.0.0` version includes **only the Box Next Generation SDK artifact**.
3032

3133
## How to decide
3234

33-
1. If you are writing a new application, use the latest major release of the SDK package.
34-
2. If you have an existing application relying on the **Next Gen SDK** and you wish to further develop your project, replace the name of this library in the package manager with the latest major release of the legacy SDK package (`v10.0.0`). Most SDKs object imports persist the same and your code will work as-is; only the TypeScript SDK requires additional steps for migrating.
35-
3. If you have an existing application relying on the **legacy SDK** and you wish to further develop your project, once released, bump the library version by one major release. See the table above, for detailed breakdown of recommended versions.
35+
1. If you are creating a new application, use `v10` of the Box core SDK package.
36+
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`). Most SDKs object imports persist the same and your code will work as-is; only the TypeScript SDK requires additional steps for migrating.
37+
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 detailed breakdown of recommended versions.
3638
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.
3739

3840
## Versioning overview
3941

4042
### Box SDK versions and artifacts
4143

42-
| SDK Package Name | Current latest version | Combined legacy and Next Gen artifacts | Next Gen SDK artifact |
43-
|--------------------|---------|--------|----------|
44-
| `box-node-sdk` | `v3.8.2` | `v4.0.0` | `v10.0.0` |
45-
| `box-python-sdk` | `v3.14.0` | `v4.0.0` | `v10.0.0` |
46-
| `box-java-sdk` | `v4.16.3` | `v5.0.0` | `v10.0.0` |
47-
| `box-windows-sdk-v2` | `v5.8.0` | `v6.0.0` | `v10.0.0` |
48-
| `box-ios-sdk` | `v5.6.0` | `v6.0.0` | `v10.0.0` |
44+
| SDK Package Name | Current latest version | Next Gen SDK artifact |
45+
|--------------------|---------|----------|
46+
| `box-node-sdk` | `v3.8.2` | `v10.0.0` |
47+
| `box-python-sdk` | `v3.14.0` | `v10.0.0` |
48+
| `box-java-sdk` | `v4.16.3` | `v10.0.0` |
49+
| `box-windows-sdk-v2` | `v5.8.0` | `v10.0.0` |
50+
| `box-ios-sdk` | `v5.6.0` | `v10.0.0` |
4951

5052
### Box Next Gen SDK deprecation status
5153

5254
| SDK Package Name | Current latest version | Note
5355
|------------------|-------------------------|-------|
54-
| `box-typescript-sdk-gen` | `v1.16.0` | deprecation in mid-August 2025, use `box-node-sdk` `v10.0.0` |
55-
| `box-python-sdk-gen` | `v1.15.0` | deprecation in mid-August 2025, use `box-python-sdk` `v10.0.0` |
56-
| `box-java-sdk-gen` | `v0.7.0` | deprecation in mid-August 2025, use `box-java-sdk` `v10.0.0` |
57-
| `box-dotnet-sdk-gen` | `v1.10.0` | deprecation in mid-August 2025, use `box-windows-sdk-v2` `v10.0.0` |
58-
| `box-swift-sdk-gen` | `v0.6.1` | deprecation in mid-August 2025, use `box-ios-sdk` `v10.0.0` |
59-
60-
Follow the change log and Box Developer blog for further instructions and announcements.
56+
| `box-typescript-sdk-gen` | `v1.19.0` | Deprecated, use `box-node-sdk` `v10.0.0` |
57+
| `box-python-sdk-gen` | `v1.17.0` | Deprecated, use `box-python-sdk` `v10.0.0` |
58+
| `box-java-sdk-gen` | `v0.8.1` | Deprecated, use `box-java-sdk` `v10.0.0` |
59+
| `box-dotnet-sdk-gen` | `v1.12.0` | Deprecated, use `box-windows-sdk-v2` `v10.0.0` |
60+
| `box-swift-sdk-gen` | `v0.6.3` | Deprecated, use `box-ios-sdk` `v10.0.0` |

‎content/guides/tooling/sdks/swift-gen.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,18 @@ alias_paths: []
1212
# Deprecated Swift SDK
1313

1414
<Message type='warning'>
15-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. **Don’t worry, your existing code will continue to work without changes**.
15+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
1616

17-
To learn more visit our SDK [versioning strategy document][versioning]
18-
</Message>
17+
Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
18+
19+
All future development, including new features and updates for Next Generation SDKs, will now be delivered through Box core SDKs starting with version `v10`.
20+
21+
For more details, see our [SDK versioning strategy document][versioning].
22+
</Message
1923

2024
You can use Box Swift SDK to call Box APIs in a Swift
2125
project.
2226

23-
<Message type='notice'>
24-
Swift SDK is in a Public Beta phase.
25-
</Message>
26-
2727
## Swift Package Manager
2828

2929
[Swift Package Manager][spm] is a tool for managing the distribution of Swift code. It is integrated with the Swift build system to automate the process of downloading, compiling, and linking dependencies.

‎content/guides/tooling/sdks/typescript-gen.md‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,14 @@ alias_paths: []
1414
# Deprecated TypeScript SDK
1515

1616
<Message type='warning'>
17-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. **Don’t worry, your existing code will continue to work without changes**.
17+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
1818

19-
To learn more visit our SDK [versioning strategy document][versioning]
20-
</Message>
19+
Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
20+
21+
All future development, including new features and updates for Next Generation SDKs, will now be delivered through Box core SDKs starting with version `v10`.
22+
23+
For more details, see our [SDK versioning strategy document][versioning].
24+
</Message
2125

2226
You can use the **auto-generated** Box TypeScript SDK to call Box APIs in a TypeScript project.
2327
This [next generation SDK][next-gen] brings along new functionality to designed to elevate the developer experience and streamline your integration with the Box Content Cloud.

‎content/pages/sdks-and-tools/index.md‎

Lines changed: 8 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ these projects to full parity.
3636

3737
### SDKs
3838

39-
The table lists legacy Box SDKs that you can use when building your
39+
The table lists Box SDKs that you can use when building your
4040
applications. For latest API support and features, use the next
4141
generation SDKs.
4242

@@ -62,26 +62,19 @@ recommend using Java SDK to build apps on Android.
6262
Refer to [this][android-docs] documentation for more details.
6363
</Message>
6464

65-
### Next generation SDKs
65+
### Next Generation SDKs
6666

6767
<Message type='warning'>
68-
In mid-August, we will be deprecating the Box Next Gen SDKs in its current form. **Don’t worry, your existing code will continue to work without changes**.
68+
As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts.
6969

70-
## Why we are making this change
70+
Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDK with no impact, but you won't receive new features, updates, or bug fixes.
7171

72-
In keeping with industry best practices, we are consolidating the Next Gen and legacy SDKs into a single package. This makes migration efforts much easier and allows you to seamlessly add new capabilities to existing applications still powered by the legacy SDKs.
72+
All future development, including new features and updates for Next Generation SDKs, will now be delivered through Box core SDKs starting with version `v10`.
7373

74-
Ultimately, the Next Generation SDKs will replace the current legacy SDKs as the latest major version release.
74+
For more details, see our [SDK versioning strategy document][versioning].
75+
</Message
7576

76-
To learn more visit our SDK [versioning strategy document][versioning]
77-
</Message>
78-
79-
The latest generation Box Python SDK, Box TypeScript
80-
SDK, .NET SDK, and Swift SDK are designed to elevate the developer
81-
experience and streamline your integration
82-
with the Box Content Cloud.
83-
84-
Here's what you can expect from the new SDKs:
77+
Here's what you can expect from generated SDKs:
8578

8679
- **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.
8780
- **Rapid API Updates**: The new auto-generation development approach allows for adding 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.

0 commit comments

Comments
 (0)