chore: Upgrade blueprint-web to v12.78.0

[jfox-box]

Summary by CodeRabbit

• Chores
  • Updated underlying UI blueprint dependencies to newer minor/patch versions to align with the latest compatibility, performance, and security improvements.
  • Includes refreshed asset packages to maintain consistency and stability across the interface.
  • No changes to user-facing features or behavior are expected as part of this update.
  • Ensures smoother future updates by keeping dependencies current without altering public interfaces.

[coderabbitai]

Walkthrough

Listen up! This PR bumps @box/blueprint-web and @box/blueprint-web-assets to newer versions in package.json, and mirrors those updates in peerDependencies. No code or API surface changes, fool.

Changes

Cohort / File(s)	Summary
Dependency bumps package.json	Updated dependencies and peerDependencies: @box/blueprint-web ^12.76.2 → ^12.78.0, @box/blueprint-web-assets ^4.68.6 → ^4.69.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: upgrade blueprint packages #4123 — Bumps the same two packages in package.json.
• feat: upgrade blueprint packages #4101 — Updates @box/blueprint-web and @box/blueprint-web-assets entries, including peers.
• fix(blueprint-web): Upgrade blueprint-web packages #4261 — Performs similar version bumps for blueprint-web packages.

Suggested labels

ready-to-merge

Suggested reviewers

• tjuanitas
• jpan-box
• greg-in-a-box

Poem

New numbers on the block, upgrades in the hood,
Blueprint rollin’ forward—dependencies look good.
No code got rocked, no APIs stirred,
Just smooth little bumps, tight and assured.
I pity the fool who fears a tidy version wood!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	I pity the fool who left only template instructions in the PR description without any actual summary of the dependency updates, motivation, or testing plan, because reviewers have no context to understand what changed or why.	Fool, fill out the description template with a clear summary of the version bumps, the rationale behind the upgrade, and any testing instructions so reviewers can easily assess and approve the PR.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	I pity the fool who complains, but this title “chore: Upgrade blueprint-web to v12.78.0” concisely and accurately summarizes the main change of bumping the blueprint-web package to v12.78.0, so reviewers scanning history will know exactly what this PR does.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

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

---

📜 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 ee8cba8 and dfe202d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (2 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: tjuanitas
PR: box/box-ui-elements#4224
File: package.json:296-297
Timestamp: 2025-08-12T18:04:17.698Z
Learning: In the box-ui-elements project, the team is comfortable with raising peerDependency minimum versions when upgrading blueprint-web packages, even if it's a breaking change for consumers.

📚 Learning: 2025-08-12T18:04:17.698Z

Learnt from: tjuanitas
PR: box/box-ui-elements#4224
File: package.json:296-297
Timestamp: 2025-08-12T18:04:17.698Z
Learning: In the box-ui-elements project, the team is comfortable with raising peerDependency minimum versions when upgrading blueprint-web packages, even if it's a breaking change for consumers.

Applied to files:

• package.json

⏰ 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: Summary
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

package.json (2)

127-128: Verify lockfile entries and Storybook build
I pity the fool who doesn't verify:

• Only one resolved version of @box/blueprint-web (^12.78.0) and @box/blueprint-web-assets (^4.69.0) in yarn.lock.
• yarn build:prod:storybook succeeds locally.

---

299-300: Confirm consumer impact and peer constraints

• Peer bump to ^12.78.0 / ^4.69.0 aligns with playbook; add a release note/PR blurb so downstreams know to upgrade.
• Verified React/React-DOM peers for @box/blueprint-web@12.78.0 (^17.0.0 || ^18.0.0) match our ^17.0.1 || ^18.0.0; Node ≥18.x engine satisfied.
• Verify @box/blueprint-web-assets@4.69.0 peerDependencies and engines manually—I pity the fool who doesn’t.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}