fix(blueprint-web): upgrade blueprint-web packages

[tjuanitas]

Summary by CodeRabbit

• Chores
  • Updated front-end UI libraries and icon assets to the latest compatible versions, broadening version ranges to accept future minor/patch releases.
  • Improves stability, compatibility, and alignment with the current design system while reducing maintenance overhead.
  • Applies to both development and peer dependencies to ensure consistent environments.
  • No feature changes; behavior should remain unchanged.

[coderabbitai]

Walkthrough

Dependency version ranges updated in package.json for devDependencies and peerDependencies: @box/blueprint-web, @box/blueprint-web-assets, and @box/item-icon. No source code modifications or API changes.

Changes

Cohort / File(s)	Summary
Dependency range updates package.json	Updated devDependencies and peerDependencies: @box/blueprint-web to ^12.57.1, @box/blueprint-web-assets to ^4.63.10, and @box/item-icon to ^0.17.13. Switched fixed versions to caret ranges to allow minor/patch updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: metadata-editor and blueprint-web-assets package bump #4137: Similar package.json bumps for @box/blueprint-web-assets and related UI packages.
• feat: upgrade blueprint packages #4101: Updates the same Blueprint packages in devDependencies/peerDependencies.
• fix(blueprint): Bump blueprint #4205: Modifies the same dependency entries including @box/item-icon.

Suggested labels

ready-to-merge

Suggested reviewers

• greg-in-a-box
• jpan-box
• tjiang-box

Poem

I nudge my deps with a gentle hop,
Carrots aligned at the version stop.
Carets sprout where pins once grew,
Patchy fields invite the new.
A bunny signs with a tidy cheer—
Ship these greens, the path is clear! 🥕✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat-upgrade-blueprint-packages

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90ee8fc and d9dc41e.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: lint_test_build
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Summary

🔇 Additional comments (2)

package.json (2)

135-135: @box/item-icon devDependency bumped — LGTM.

No concerns for local development and storybook.

---

303-303: Peer min bump for @box/item-icon may exclude existing consumers.

Moving from ^0.17.0 to ^0.17.13 raises the minimum. If not strictly required, keep the lower bound to avoid forcing consumer upgrades.

-    "@box/item-icon": "^0.17.13",
+    "@box/item-icon": ">=0.17.0 <0.18",

If the bump is required due to APIs/assets used, please note it as a breaking change in the release notes.

[tjuanitas]

we need to review the blueprint modals since there's an issue with padding. tbh I think we should update the ContentExplorer modals to use the new design