chore: package bump metadata-editor

[box-catzhang]

Summary by CodeRabbit

• Chores
  • Updated the "@box/metadata-editor" dependency to a newer version.

[coderabbitai]

Walkthrough

The pull request updates the version of the @box/metadata-editor package from ^0.112.0 to ^0.115.0 in the devDependencies, peerDependencies, and dependencies sections of the package.json file. No other changes are present.

Changes

File(s)	Change Summary
package.json	Bumped @box/metadata-editor from ^0.112.0 to ^0.115.0 in all relevant dependency sections.

Possibly related PRs

• feat: metadata-editor and blueprint-web-assets package bump #4137: Also updates the version of @box/metadata-editor in package.json, continuing the version bump.
• feat(metadata-editor): expose advanced metadata extract agent props #4128: Updates @box/metadata-editor and introduces new props and code changes related to metadata extract agents.

Suggested labels

ready-to-merge

Suggested reviewers

• patlm
• tjuanitas

Poem

A hop and a skip, a version hops high,
Metadata-editor waves the old goodbye.
From one-one-two to one-one-five,
Dependencies fresh, the code will thrive.
Rabbits rejoice with a jubilant cheer—
Updates like these bring springtime near! 🐇✨

---

📜 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 15c5d8d and 1bb0aaa.

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

• GitHub Check: lint_test_build
• GitHub Check: Summary

🔇 Additional comments (2)

package.json (2)

136-136: Bump @box/metadata-editor in devDependencies
Version updated from ^0.112.0 to ^0.115.0 under devDependencies. Ensure your lockfile (yarn.lock or package-lock.json) is regenerated and CI passes against this change.

---

305-305: Bump @box/metadata-editor in peerDependencies
Version updated from ^0.112.0 to ^0.115.0 under peerDependencies. Verify that downstream consumers are compatible with this release and update any relevant integration docs.

---

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