Bump @wordpress/edit-post from 8.5.0 to 8.7.0

[acicovic]

Description

Updates @wordpress/edit-post from 8.5.0 to 8.7.0. Replaces #2746 as the update of @types/wordpress__edit-post was causing issues.

Motivation and context

Update dependencies while keeping our sanity.

How has this been tested?

The builds that fail in #2746 succeed here.

Summary by CodeRabbit

• New Features

  • Upgraded the WordPress edit post package, potentially introducing new features and improvements.

• Bug Fixes

  • The update may resolve existing issues from the previous version, enhancing overall performance and stability.

[coderabbitai]

Walkthrough

Walkthrough

This pull request updates the version of the @wordpress/edit-post package in the package.json file from ^8.5.0 to ^8.7.0. This change indicates an upgrade to a newer version of the package, which may include various updates such as new features, bug fixes, or performance enhancements.

Changes

File	Change Summary
package.json	Updated @wordpress/edit-post from ^8.5.0 to ^8.7.0

Possibly related PRs

• Manually update npm dependencies #2473: Involves updates to the package.json file, including dependency management for Gutenberg components, related to the @wordpress/edit-post version update.
• Update data, core-data and editor WordPress packages #2540: Updates multiple @wordpress packages, including @wordpress/editor, relevant to the changes in the main PR.
• Bump @wordpress/editor from 14.5.0 to 14.7.0 #2769: Updates the @wordpress/editor package, closely related to the changes made regarding the @wordpress/edit-post package version update.

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 557f090 and 55cb7c8.

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)

66-66: Approved version update for @wordpress/edit-post.

The update from ^8.5.0 to ^8.7.0 is noted and appears to be in line with the project's goals of maintaining updated dependencies.

However, it's crucial to ensure that this update integrates well with the rest of the project and does not introduce any new issues, especially since previous attempts to update this package were problematic.

Run the following script to verify the compatibility and stability of the new package version: