SDK consolidated version release #846
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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 Box Next Generation SDKs, will be delivered through 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`. | ||
|
|
||
| For more details, see our [SDK versioning strategy document][versioning]. | ||
|
|
||
| [versioning]: g://tooling/sdks/sdk-versioning | ||
| [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-v10.md | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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 Box Next Generation SDKs, will be delivered through 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].** | ||||||
|
||||||
| **All future development, including new features and updates for the Box Next Generation SDKs, will be delivered through 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].** | |
| **All future development, including new features and updates for the Box Next Generation SDKs, 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].** |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -13,63 +13,90 @@ alias_paths: [] | |||||
|
|
||||||
| # Box SDK versioning strategy | ||||||
|
|
||||||
| Box core SDKs and Box Next Generation SDKs were created as separate libraries. However, 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 older versions of Box core SDKs, which were maintained manually. | ||||||
|
||||||
|
|
||||||
| To facilitate this migration process, there are two actively maintained major Box core SDK versions: | ||||||
|
|
||||||
| - **the current major version which includes:** the manually maintained package and the generated one. This SDK version enables leveraging coexisting packages at the same time, and serve as a transition phase. This version of Box SDK will be supported until 2027. | ||||||
|
||||||
| - **the current major version which includes:** the manually maintained package and the generated one. This SDK version enables leveraging coexisting packages at the same time, and serve as a transition phase. This version of Box SDK will be supported until 2027. | |
| - **The current major version** which 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. This version of Box SDK will be supported until 2027. |
Outdated
There was a problem hiding this comment.
The current major version - current is not the best word. v10 is now the current. Maybe sth like: The major version ?
Outdated
There was a problem hiding this comment.
"This version is available as a branch for each Box core SDK repository." combined version is also available as a separate branch. Maybe we don't need that sentence here
Outdated
There was a problem hiding this comment.
If we want to leave it as a question, we need a question mark at the end. Unless we want to make it a statement, then rewrite as: "What it means for your project"
Outdated
There was a problem hiding this comment.
"... covenience methods, new features..." - do you mean to say "Start leveraging convenience methods AND new features..." or something else?
Outdated
There was a problem hiding this comment.
Action is not rendered correctly if you tried to achieve bolding
There was a problem hiding this comment.
Is it going to be displayed this way? I don't like that you have to scroll to the right to read it all.
There was a problem hiding this comment.
This is component specific pill that we have across the project, I think it makes it more prominent.
Outdated
There was a problem hiding this comment.
I would add one more case:
App using both Box Next Generation SDK and old sdk -> use combined SDK
Outdated
There was a problem hiding this comment.
Suggested 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. | |
| **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. |
Outdated
There was a problem hiding this comment.
Suggested change
| | Repository name | Artifact name | Includes both packages | Includes the only generated package| | |
| | Repository name | Artifact name | Includes both packages | Includes generated package only| |
mwwoda marked this conversation as resolved.
Show resolved
Hide resolved
mwwoda marked this conversation as resolved.
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Suggested change
| **All future development, including new features and updates for the Box Next Generation SDKs, will be delivered through 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.** | |
| **All future development, including new features and updates for the Box Next Generation SDKs, 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.** |
Outdated
There was a problem hiding this comment.
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
Outdated
There was a problem hiding this comment.
Suggested change
| Follow detailed migrations guides to migrate from from Box Next Generation SDKs to Box core SDK `v10`: | |
| Follow detailed migration guides to migrate from from the Box Next Generation SDKs to the Box core SDK `v10`: |
mwwoda marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
mwwoda marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
mwwoda marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
mwwoda marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.