Bump @wordpress/editor from 14.7.0 to 14.8.3

[acicovic]

Description

Updates @wordpress/editor from 14.7.0 to 14.8.3. Replaces #2788 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 #2788 succeed here.

Summary by CodeRabbit

• New Features

  • Updated the WordPress editor package to the latest version, potentially introducing new features and improvements.

• Bug Fixes

  • Included bug fixes and performance enhancements from the updated editor package.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The package.json file for the wp-parsely project has been updated to reflect a change in the version of the @wordpress/editor dependency, which has been incremented from ^14.7.0 to ^14.8.3. This modification indicates an upgrade to the editor package. No other dependencies or fields within the package.json have been altered.

Changes

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

Possibly related PRs

• Update WordPress typing packages #2841: Updates the @types/wordpress__editor package, related to the same WordPress editor functionality.
• Bump @wordpress/editor from 14.8.3 to 14.9.0 #2839: Further updates the @wordpress/editor dependency from ^14.8.3 to ^14.9.0, directly related to the current PR.
• Bump @wordpress/editor from 14.7.0 to 14.8.3 #2815: Involves updating the version of the @wordpress/editor dependency in package.json from ^14.7.0 to ^14.8.3, directly related to the current PR.

Suggested labels

Component: Dependencies

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5fb3b4 and 7b70959.

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

---

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.
  • 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 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 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.