feat: upgrade blueprint packages

[tjuanitas]

Summary by CodeRabbit

• Chores
  • Updated dependency versions for improved compatibility and stability.

[coderabbitai]

Walkthrough

The package.json file was updated to increase the versions of the @box/blueprint-web and @box/blueprint-web-assets dependencies in both the devDependencies and peerDependencies sections. No other changes were made to the file or to exported entities.

Changes

File	Change Summary
package.json	Bumped @box/blueprint-web from ^10.3.1 to ^11.12.0 and @box/blueprint-web-assets from ^4.39.0/^4.36.0 to ^4.44.1 in both devDependencies and peerDependencies.

Poem

The blueprint’s grown, the assets, too—
With numbers higher, fresh and new.
A hop, a skip, dependencies rise,
In the garden of code, a sweet surprise.
🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 15c403c and bc074b2.

⛔ 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 (3)

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

🔇 Additional comments (2)

package.json (2)

128-129: Verify major version upgrade for @box/blueprint-web and @box/blueprint-web-assets in devDependencies
You’ve bumped @box/blueprint-web from ^10.3.1 to ^11.12.0 (major) and @box/blueprint-web-assets from ^4.39.0 to ^4.44.1. Major upgrades can introduce breaking changes—please run the full test suite, perform smoke tests in Storybook/examples, and consult the migration guide to confirm compatibility.

---

302-303: Ensure peerDependencies align with the new devDependencies versions
Updating both dev and peer dependencies to @box/blueprint-web@^11.12.0 and @box/blueprint-web-assets@^4.44.1 is the right move for consistency. Verify that downstream consumers resolve to a single version without conflicts, and update any documentation or changelogs that specify supported versions.

---

🪧 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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• 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.

[tjuanitas]

@coderabbitai are you able to identify the breaking changes between the major version for the @box/blueprint-web packages? here is the npm link to the package: https://www.npmjs.com/package/@box/blueprint-web

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

I'll check for information about the breaking changes between the major versions of @box/blueprint-web package. Let me search for that.

---

🌐 Web query:

@box/blueprint-web major version changes from 10 to 11 changelog or breaking changes

💡 Result:

There is no official changelog or detailed list of breaking changes for the major version update from 10 to 11 for the @box/blueprint-web package found in the provided search results. The npm package page for @box/blueprint-web mentions that pull requests (PRs) with changes are linked in the changelog to aid understanding and migration, but the actual changelog or migration notes for the version jump from 10 to 11 are not directly referenced or visible in the search results[1].

If you need to confirm specific breaking changes between versions 10 and 11, the following steps are recommended:

• Check the package's repository: The official changelog or GitHub releases tab for the package often contains detailed notes for major version changes. Search specifically for version 10.x.x and 11.x.x release notes.
• Review linked PRs: Pull requests mentioned in changelogs or release notes may include migration guides or highlight breaking changes for major version updates.
• Consult usage guidelines: If the changelog states migration/usage guidelines are included with PRs, reviewing those PRs will provide insight into major updates or necessary code changes[1].

Given the absence of direct information in the search results, you may need to access the repository or npm package changelog manually for the most up-to-date and authoritative details.

Citations:

• 1: https://www.npmjs.com/package/@box%2Fblueprint-web
• 2: https://developer.box.com/changelog/
• 3: https://github.com/box/box-java-sdk/blob/main/CHANGELOG.md
• 4: https://community.box.com/general-15/box-community-weekly-digest-april-11-2025-3891
• 5: https://github.com/box/box-content-preview/blob/master/CHANGELOG.md
• 6: https://canvas.workday.com/help/upgrade-guides/canvas-v11-upgrade-guide
• 7: https://metabox.io/changelog/
• 8: https://docs.ckan.org/en/2.11/changelog.html
• 9: https://github.com/box/box-ui-elements/blob/master/package.json
• 10: https://remix.run/docs/en/main/start/changelog

---

🏁 Script executed:

#!/bin/bash
# Look for any CHANGELOG files that might mention blueprint web changes
fd CHANGELOG --type f

# Search for files that might contain information about blueprint upgrades
rg -i "blueprint.*(upgrade|migration|breaking changes)" --type=md

# Check if there are any direct mentions of blueprint v11 breaking changes
rg -i "blueprint.*v11" --type=md
rg -i "blueprint.*11\.0" --type=md
rg -i "blueprint.*breaking" --type=md

# Look specifically in the docs directory if it exists
fd . docs --type=f | grep -i blueprint

# Check if there are any npm scripts related to blueprint
cat package.json | jq '.scripts' | grep -i blueprint

Length of output: 389

---

🏁 Script executed:

#!/bin/bash
# Check the exact version changes in package.json
cat package.json | grep -A 3 -B 3 "blueprint-web"

# Look for any files that mention blueprint
rg -i "blueprint" --type=js --type=jsx --type=ts --type=tsx -l | head -10

# Check if there's a blueprint implementation file that might have version-specific code
rg -i "from.*blueprint" --type=js --type=jsx --type=ts --type=tsx | head -10

# See if we can find the GitHub repository URL for blueprint-web in package.json or other files
rg -i "github.*blueprint" --type=json

Length of output: 941

---

🏁 Script executed:

#!/bin/bash
# Look at the PR changes to see the exact version changes
git diff --unified=5 HEAD^1 -- package.json

# Look for files that mention blueprint without using file type flags
rg -i "blueprint" -l | head -15

# Check for any imports from blueprint packages
rg -i "import.*(from|require).*blueprint" | head -15

# Search for README files that might mention blueprint
fd README --type=f | xargs grep -i "blueprint" || echo "No mentions in README files"

Length of output: 2599

---

🏁 Script executed:

#!/bin/bash
# Get diff of the current PR
git diff HEAD $(git merge-base HEAD master) -- package.json

# Search for blueprint in all relevant files to find any version-specific code
rg -i "blueprint.*10|blueprint.*11" | head -15

# Look for any commit messages that might reference blueprint upgrades
git log --grep="blueprint" --oneline -n 10

# Check if there are any specific imports that might have changed in recent commits
git diff HEAD $(git merge-base HEAD master) | grep -i "blueprint"

Length of output: 620

---

🏁 Script executed:

#!/bin/bash
# Get the exact version change in package.json by getting the state before and after
git show HEAD:package.json | grep -A 2 -B 2 "blueprint-web"
git show $(git merge-base HEAD origin/master):package.json | grep -A 2 -B 2 "blueprint-web" || echo "Not found in base"

# Look for package.json in the PR commit
git diff --name-only HEAD $(git merge-base HEAD origin/master) | grep package.json

# Try to find the repository URL for the blueprint package
npm view @box/blueprint-web repository.url homepage 2>/dev/null || echo "Package info not available"

# Try to find any information about the blueprint package from the package.json
git show HEAD:package.json | grep -i "blueprint" -A 5 -B 5

Length of output: 2290

---

🏁 Script executed:

#!/bin/bash
# Try to get the diff from the PR
git diff -U3 bc074b26a5a806988476d90f9b814b037dcb3f79 15c403c402e135ff9f5f73da011633d6ac923e3d -- package.json

# Check yarn.lock for old versions
grep -A 5 -B 5 "blueprint-web@\^10" yarn.lock || echo "Version 10 not found in yarn.lock"
grep -A 5 -B 5 "blueprint-web@\^11" yarn.lock

# Try to find any related pull requests or commits
git log -n 20 --oneline | grep -i "blueprint\|upgrade"

# Also check import statements to see if any components might have changed
git diff -G "import.*blueprint" bc074b26a5a806988476d90f9b814b037dcb3f79 15c403c402e135ff9f5f73da011633d6ac923e3d || echo "No import changes found"

Length of output: 2068

---

@tjuanitas I've looked into the breaking changes between versions 10.3.1 and 11.12.0 of @box/blueprint-web, but couldn't find specific documentation. Here's what I discovered:

1. The PR upgrades:

   • @box/blueprint-web from ^10.3.1 to ^11.12.0
   • @box/blueprint-web-assets from ^4.39.0 to ^4.44.1 (dev) and ^4.36.0 to ^4.44.1 (peer)

2. Your codebase uses several Blueprint components including TooltipProvider, LoadingIndicator, Text, Accordion, InlineError, IconButton, and others.

Since I couldn't find public documentation on the breaking changes, here are some recommended steps:

1. Check if @box/blueprint-web has an internal repository with migration guides
2. Review the package's GitHub releases/commits between v10 and v11 if accessible
3. Create a test branch to:
   • Perform the upgrade
   • Run all tests
   • Check for console warnings/errors
   • Verify components render correctly
4. Look for dependency changes (v11 uses "@ariakit/[email protected]")

There don't appear to be any import changes in this PR, which suggests the component APIs might be compatible, but thorough testing is still recommended given this is a major version upgrade.