Bump @wordpress/editor from 14.5.0 to 14.7.0

[acicovic]

Description

Updates @wordpress/editor from 14.5.0 to 14.7.0. Replaces #2745 as the update of @types/wordpress__editor was causing issues.

Motivation and context

Update dependencies while keeping our sanity.

How has this been tested?

The builds that fail in #2745 succeed here.

Summary by CodeRabbit

• New Features
  • Upgraded the WordPress editor package, potentially introducing new features and improvements for enhanced editing capabilities.

[coderabbitai]

Walkthrough

Walkthrough

This pull request updates the version of the @wordpress/editor package in the package.json file from ^14.5.0 to ^14.7.0. This change reflects a transition to a newer version, which may include various updates such as bug fixes, new features, or performance improvements.

Changes

File	Change Summary
package.json	Updated @wordpress/editor version from ^14.5.0 to ^14.7.0

Possibly related PRs

• Manually update npm dependencies #2473: Involves updates to package.json, including an override for a package related to the main PR's update.
• Update data, core-data and editor WordPress packages #2540: Directly updates the @wordpress/editor package version, closely related to the main PR.
• Revert to using babel-preset-default v7 #2537: Updates the version of @wordpress/babel-preset-default, impacting overall package management.
• Update minimum node and npm versions #2541: Updates minimum required versions for Node.js and npm, relevant to the environment for the updated package.

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fe5748a and e8bf1dd.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

67-67: Dependency version update approved, verify compatibility.

The update of @wordpress/editor from ^14.5.0 to ^14.7.0 is approved as it likely includes beneficial improvements. However, it's crucial to verify that this update is compatible with other dependencies and the overall project setup.

Run the following script to verify compatibility with other dependencies:

Verification successful

---

Dependency version update verified, recommend further testing.

The update of @wordpress/editor to ^14.7.0 is consistent across the codebase, and no immediate conflicts with other dependencies were found. However, it is recommended to conduct further manual testing to ensure full compatibility and integration with the rest of the project.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of updated `@wordpress/editor` with other dependencies.

# Test: Check for known issues or conflicts with other dependencies.
rg --type json -A 5 $'@wordpress/editor'

Length of output: 2393