-
Notifications
You must be signed in to change notification settings - Fork 91
SDK consolidated version release #846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
||
| - `(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 which includes consolidated packages. Start leveraging convenience methods, new features thanks to the generated package, and gradually migrate your code base. Check version breakdown for each programming language. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Action is not rendered correctly if you tried to achieve bolding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is component specific pill that we have across the project, I think it makes it more prominent.
| 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 ≥`v10.0.0` of the Box core SDK package. | ||
| </Tile> | ||
| <Tile type="info" title="4. No Active Development" href="/guides/tooling/sdks/sdk-versioning/#box-core-sdk-versions-and-artifacts-overview"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add one more case:
App using both Box Next Generation SDK and old sdk -> use combined SDK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| - Swift | ||
|
|
||
| ### Migrating from Box Next Generations SDKs to core Box SDK `v10` | ||
| ### Migrating from Box Next Generation SDKs to core Box SDK `v10` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Migrating from Box Next Generation SDKs
This is because you can either migrate to v10 ( if you were using just next gen sdk) of combined version (if you were using next gen along with old SDK) - we will have these two case covered in the mogration guide
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess some links for our migration guides are a bit inconsistent in the SDK repos
Nevermind, some migration guides are still not done on our side. But .NET and Swift are ready
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a couple of final suggestions.
content/guides/tooling/sdks/index.md
Outdated
| 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| SDK, Box .NET SDK, and Box Swift SDK is designed to elevate the developer | |
| SDK, Box .NET SDK, and Box Swift SDK are designed to elevate the developer |
We are enumerating different SDKs, so we need to have a plural verb here (AND).
| **Action** Replace the library name in your package manager with Box core SDK package (≥`v10.0.0`). Check migration guides for detailed instructions. | ||
| </Tile> | ||
| <Tile type="branch" title="3. Existing App - Box core SDK and the Box Next Generation SDK" href="/guides/tooling/sdks/sdk-versioning/#migration-to-the-generated-package"> | ||
| If you have an existing application that relies both on Box core SDK and Next Generation SDK: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| If you have an existing application that relies both on Box core SDK and Next Generation SDK: | |
| If you have an existing application that relies both on the Box core SDK and the Next Generation SDK: |
| Box core SDKs and Box Next Generation SDKs were created as separate libraries. Going forward, the Box core SDK artifacts will include: | ||
| <TileGrid rows="2"> | ||
| <Tile type="cog" title="1. Existing App - Box core SDK" href="/guides/tooling/sdks/sdk-versioning/#migration-to-the-generated-package"> | ||
| If you have an existing application that relies on Box core SDK and you wish to further develop your project: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| If you have an existing application that relies on Box core SDK and you wish to further develop your project: | |
| If you have an existing application that relies on the Box core SDK and you wish to further develop your project: |
| 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 which includes consolidated packages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| **Action** Use the major version which includes consolidated packages. | |
| **Action** Use the major version that includes consolidated packages. |
|
|
||
| - `(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 which includes consolidated packages. Start using convenience methods and new features from the generated package, and gradually migrate your codebase. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| **Action** Use the major version which includes consolidated packages. Start using convenience methods and new features from the generated package, and gradually migrate your codebase. | |
| **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. |
| <Tile type="info" title="5. No Active Development" href="/guides/tooling/sdks/sdk-versioning/#box-core-sdk-versions-and-artifacts-overview"> | ||
| If you have an existing application that you don't plan to change: | ||
|
|
||
| **Action** Ensure your package manager includes the specific version of the SDK version to prevent accidental updates. We strongly recommend upgrading to the major version, which includes consolidated packages, to receive ongoing security patches and improvements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| **Action** Ensure your package manager includes the specific version of the SDK version to prevent accidental updates. We strongly recommend upgrading to the major version, which includes consolidated packages, to receive ongoing security patches and improvements. | |
| **Action** Ensure your package manager includes the specific SDK version to prevent accidental updates. We strongly recommend upgrading to the major version, which includes consolidated packages, to receive ongoing security patches and improvements. |
|
|
||
| ### Migration from Box Next Generation SDKs | ||
|
|
||
| Follow detailed migration guides to migrate from from the Box Next Generation SDKs to the Box core SDK `v10`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Follow detailed migration guides to migrate from from the Box Next Generation SDKs to the Box core SDK `v10`: | |
| Follow detailed migration guides to migrate from the Box Next Generation SDKs to the Box core SDK `v10`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor changes.
| # 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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. | |
| 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. |
| 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. 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - **A major version that follows sequential versioning for each SDK artifact. 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. | |
| - **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. |
"in 2027" or "until 2027"?
|
|
||
| ## Why we are making this change | ||
| - **A major version that follows sequential versioning for each SDK artifact. 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` includes **only the generated package**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - `v10` includes **only the generated package**. | |
| - `v10` that includes **only the generated package**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

Description
Please include a summary of the change and which issue is fixed.
If you are a Boxer, please also reference the related
DDOCorAPIWGtickets.If you do not have a related
Jiraticket and this is more than a bug fix, thencreate one now.
Fixes # (issue)
Re
DDOC-#(Jiraticket)Re
APIWG-#(Jiraticket)Checklist
yarn lintto make sure my changes pass all lintersContribution guidelines
For contribution guidelines, styleguide, and other helpful information please
see the
CONTRIBUTING.mdfile in the root of this project.