Box iOS SDK 10.0.1 released

Bug Fixes

• Allow flexible key-value data in AiExtractResponse.answer and Event.additionalDetails (box/box-openapi#556) (#1128) (3e9a78c)
• Make role parameter of update collaboration optional (box/box-openapi#557) (#1138) (3fc5dc9)

Box Java SDK v10.1.0 released

Bug Fixes

• Allow flexible key-value data in AiExtractResponse.answer and Event.additionalDetails (box/box-openapi#556) (#1470) (e215a5f)
• Make role parameter of update collaboration optional (box/box-openapi#557) (#1479) (6896386)

New Features and Enhancements

• Add Javadoc comments (box/box-codegen#839) (#1465) (c72407d)

Box Node SDK v10.0.1 released

Bug Fixes

• Allow flexible key-value data in AiExtractResponse.answer and Event.additionalDetails (box/box-openapi#556) (#1051) (70a2275)
• Make role parameter of update collaboration optional (box/box-openapi#557) (#1068) (3992171)
• Relax JSON deserialization guard by removing strict content-type check (box/box-codegen#844) (#1033) (1eb2c32)

Box Windows SDK v10.1.0 released

Bug Fixes

• Allow flexible key-value data in AiExtractResponse.answer and Event.additionalDetails (box/box-openapi#556) (#1147) (c41a444)
• Make role parameter of update collaboration optional (box/box-openapi#557) (#1156) (8247918)

New Features and Enhancements

• Handle Dictionary with object values deserialization (box/box-codegen#850) (#1144) (611b474)

Box Python SDK v10.0.1 released

Bug Fixes

• Allow flexible key-value data in AiExtractResponse.answer and Event.additionalDetails (box/box-openapi#556) (#1084) (f63cffe)
• Make role parameter of update collaboration optional (box/box-openapi#557) (#1093) (5c21907)

Box Java SDK v4.16.4 released

Bug Fixes

• Bump Bouncy Castle to fix CVE-2025-8916 (#1454) (a3605f4)

Salesforce Developer Toolkit updates

The developer guides for the Salesforce Developer Toolkit have been updated to include:

• Methods and operations for Box Sign and Box Hubs
• Code samples for Box Sign and Box Hubs
• All methods that can be invoked in Salesforce Flows
• Methods in Agentforce Flows for Box Hubs

Box CLI v4.3.1 released

Bug Fixes

• Fix multi item mode in ai:ask command (#593) (5081d43)

Box UI Elements v25.0.0 released

25.0.0 (2025-09-26)

Bug Fixes

• classification: use AsyncLoad for AppliedByAiClassificationReason (#4274) (b80df38)
• common: Remove findDOMNode from makeDroppable (BREAKING CHANGE) (#4276) (c3bcad3)
• i18n: update translations (#4269) (d27c054)
• i18n: update translations (#4272) (9f3520b)
• i18n: update translations (#4277) (23b27f6)
• i18n: update translations (#4280) (7c633b8)
• i18n: update translations (#4289) (8453128)
• metadata-view: show error state when exception is thrown (#4270) (246f2df)
• metadataeditor: portal dropdown to preview container (#4273) (540a957)

Features

• classification: AppliedByAiClassificationReason card to support empty reason (#4279) (cb04234)
• classification: support AI reasoning and new applied by labels (#4271) (681bace)
• content-sharing: Create ContentSharingV2 component (#4282) (ef49c77)
• metadata-view: bump metadata view version (#4287) (f5887d7)
• metadata-view: update blueprint web version (#4288) (6d599a3)
• timestamped-comments: enable timestamp handling in sidebar (#4275) (7f9defa), closes #4226 #4230 #4274
• timestamped-comments: timestamped comments editor updates (#4244) (6e1bd80), closes #4226 #4230

BREAKING CHANGES

• common: Wrapped component of makeDroppable must have ref prop,

for example with React.forwardRef

• fix: Clean up tests

Metadata view v2 in Content Explorer

We introduced v2 of the metadata view in the Box Content Explorer UI element. It's a ground-up redesign of the original version, introducing a streamlined interface tailored for metadata-driven workflows.

Key features

• filtering and editing interfaces with dedicated UI for each metadata field type,
• flexible display options with list and grid views,
• pagination support.

Migration from v1 to v2

The v1 of the metadata view Content Explorer has reached end of support and it will no longer receive bug fixes or new features. We recommend to migrate to the new v2 metadata view. See the migration guide for a detailed instruction.

Where to get support

Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.