Bump @wordpress/edit-post from 8.8.3 to 8.9.0

[acicovic]

Description

Updates @wordpress/edt-post from 8.8.3 to 8.9.0. Replaces #2834 as the update of @types/wordpress__edit-post was causing issues.

Also updates other deps not handled by dependabot, by running npm update and a few npm dedupe commands.

Motivation and context

Update dependencies while keeping our sanity.

How has this been tested?

The builds that fail in #2834 succeed here.

Summary by CodeRabbit

• New Features
  • Updated the @wordpress/edit-post dependency to version ^8.9.0, potentially introducing new features and improvements.
• Chores
  • Incremented package version to 3.16.4.

[coderabbitai]

📝 Walkthrough

Walkthrough

The package.json file for the wp-parsely project has been updated to version 3.16.4. The primary change involves upgrading the @wordpress/edit-post dependency from version ^8.8.3 to ^8.9.0. This update indicates a shift to a newer version of the package, while all other dependencies and development dependencies remain unchanged, with no alterations made to scripts, engines, or other metadata.

Changes

File	Change Summary
package.json	Updated @wordpress/edit-post from ^8.8.3 to ^8.9.0; version incremented to 3.16.4.

Possibly related PRs

• Bump @wordpress/edit-post from 8.5.0 to 8.7.0 #2770: This PR updates the @wordpress/edit-post package from version 8.5.0 to 8.7.0, which is directly related to the main PR that updates the same package from ^8.8.3 to ^8.9.0.
• build(deps-dev): bump @wordpress/block-editor from 13.3.0 to 14.0.0 #2697: This PR updates the @wordpress/block-editor package from ^13.3.0 to ^14.0.0, which is relevant as it involves a similar dependency management context within the package.json.
• Bump @wordpress/editor from 14.8.3 to 14.9.0 #2839: This PR updates the @wordpress/editor package from ^14.8.3 to ^14.9.0, which is also related to the dependency management aspect of the main PR.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 407d037 and 14c7c52.

⛔ 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 context used

🔇 Additional comments (2)

package.json (2)

Line range hint 3-3: LGTM: Version update is appropriate.

The project version has been incremented to 3.16.4, which is consistent with updating dependencies. This change aligns with the PR objectives.

---

66-66: LGTM: Dependency update matches PR objectives.

The @wordpress/edit-post dependency has been correctly updated from ^8.8.3 to ^8.9.0. This change is consistent with the PR objectives and maintains the caret for compatible updates.

To ensure no unintended changes were made, let's verify the package-lock.json file:

✅ Verification successful

To complete the verification process, we need to check the specific entry for @wordpress/edit-post in the package-lock.json file. Let's run a targeted search for this package.

---

Dependency update successfully verified

The update of @wordpress/edit-post from 8.8.3 to 8.9.0 has been correctly implemented in both package.json and package-lock.json files. The package-lock.json file shows the entry "@wordpress/edit-post": "^8.9.0", which matches the intended update and maintains the correct versioning format with the caret (^) for potential minor and patch updates.

This change aligns perfectly with the PR objectives, and no issues were found in the implementation of this dependency update.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that only @wordpress/edit-post was updated in package-lock.json

# Test: Check for changes in package-lock.json
# Expect: Only @wordpress/edit-post should be updated
rg --json '"@wordpress/edit-post"' package-lock.json | jq -r '.data.lines.text' | grep -E '("version"|"resolved")'

# Test: Check for any other changes in package-lock.json
# Expect: No other packages should be updated
rg --json -v '"@wordpress/edit-post"' package-lock.json | jq -r '.data.lines.text' | grep -E '("version"|"resolved")' | sort | uniq -c

Length of output: 181194

---

Script:

#!/bin/bash
# Search for @wordpress/edit-post in package-lock.json and display its entry
grep -A 10 '"@wordpress/edit-post":' package-lock.json

Length of output: 449

---

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