Update version number and changelog for 3.14.5 release

[acicovic]

This PR updates the plugin's version number and changelog in preparation for the 3.14.5 release.

Fixed

• Fix: Make PCH Related Posts filters work for non-admins (#2467)

Summary by CodeRabbit

• New Features

  • Enhanced the related posts panel to include author availability checks, improving content filtering for users.

• Bug Fixes

  • Fixed an issue allowing non-admin users to use PCH Related Posts filters.

• Documentation

  • Updated documentation and version references across various files to reflect the new version 3.14.5.

• Tests

  • Updated end-to-end tests to use the new plugin version 3.14.5.

[coderabbitai]

Walkthrough

Walkthrough

Version 3.14.5 of the project introduces a fix to enhance the functionality of PCH Related Posts for non-admin users, updates various files to reflect the new version number, and improves conditions and filters in the codebase related to the handling of post data and author availability.

Changes

File Path	Change Summary
CHANGELOG.md, README.md, package.json, wp-parsely.php, tests/e2e/utils.ts	Updated version number from 3.14.4 to 3.14.5
src/.../component.tsx, src/.../hooks.ts	Enhanced handling of author availability and post data filters; added context: 'view' parameter

Possibly related issues

• Release wp-parsely 3.14.5 #2468: This issue tracks the release process of wp-parsely 3.14.5, which aligns with the updates and version changes noted in this PR.
• Release wp-parsely 3.14.4 #2462: Although this issue tracks the previous version release (3.14.4), understanding its process might provide insights or necessary steps that were also considered in the latest 3.14.5 release process.

---

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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

[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 54274e0 and 384479b.

Files ignored due to path filters (3)

• build/content-helper/editor-sidebar.asset.php is excluded by !build/**
• build/content-helper/editor-sidebar.js is excluded by !build/**
• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (7)

• CHANGELOG.md (1 hunks)
• README.md (1 hunks)
• package.json (1 hunks)
• src/content-helper/editor-sidebar/related-posts/component.tsx (3 hunks)
• src/content-helper/editor-sidebar/related-posts/hooks.ts (3 hunks)
• tests/e2e/utils.ts (1 hunks)
• wp-parsely.php (2 hunks)

Files skipped from review due to trivial changes (3)

• package.json
• tests/e2e/utils.ts
• wp-parsely.php

Additional Context Used

LanguageTool (10)

README.md (10)

Near line 5: Do not use a colon (:) before a series that is introduced by a preposition (‘to’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ....5 Requires at least: 5.2 Tested up to: 6.5 Requires PHP: 7.2 License: GPLv...

---

Near line 43: Unpaired symbol: ‘[’ seems to be missing
Context: ...g edited such as: - [Title Suggestions](https://docs.wpvip.com/parse-ly/wp-pars...

---

Near line 44: Unpaired symbol: ‘[’ seems to be missing
Context: ...rrently being edited. - [Smart Linking](https://docs.wpvip.com/parse-ly/wp-pars...

---

Near line 45: Unpaired symbol: ‘[’ seems to be missing
Context: ...top-performing posts. - [Related Posts](https://docs.parse.ly/plugin-content-he...

---

Near line 46: Unpaired symbol: ‘[’ seems to be missing
Context: ...tly being edited. - [Performance Stats](https://docs.parse.ly/plugin-content-he...

---

Near line 59: ‘Last but not least’ might be wordy. Consider a shorter alternative.
Context: ... and WP Rest API) setups is included. - Last but not least, a wide range of hooks is available in ...

---

Near line 59: Consider a shorter alternative to avoid wordiness.
Context: ...ast, a wide range of hooks is available in order to customize the plugin's functionality ev...

---

Near line 63: Unpaired symbol: ‘[’ seems to be missing
Context: ...n and resources - [Plugin Documentation](https://docs.parse.ly/wordpress-plugin-...

---

Near line 64: Unpaired symbol: ‘[’ seems to be missing
Context: ...gin-setup/). - [Commonly Asked Questions](https://docs.parse.ly/plugin-common-que...

---

Near line 65: Unpaired symbol: ‘[’ seems to be missing
Context: .../plugin-common-questions/). - [Changelog](https://github.com/parsely/wp-parsely/b...

Path-based Instructions (2)

src/content-helper/editor-sidebar/related-posts/hooks.ts (1)

Pattern **/*.{js,ts,tsx,jsx}: "Perform a detailed review of the provided code with following key aspects in mind:

• Review the code to ensure it is well-structured and adheres to best practices.
• Verify compliance with WordPress coding standards.
• Ensure the code is well-documented.
• Check for security vulnerabilities and confirm the code is secure.
• Optimize the code for performance, removing any unnecessary elements.
• Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
• Ensure each line comment concludes with a period.
• Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
• Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features."

src/content-helper/editor-sidebar/related-posts/component.tsx (1)

Pattern **/*.{js,ts,tsx,jsx}: "Perform a detailed review of the provided code with following key aspects in mind:

• Review the code to ensure it is well-structured and adheres to best practices.
• Verify compliance with WordPress coding standards.
• Ensure the code is well-documented.
• Check for security vulnerabilities and confirm the code is secure.
• Optimize the code for performance, removing any unnecessary elements.
• Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
• Ensure each line comment concludes with a period.
• Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
• Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features."

Additional comments not posted (7)

src/content-helper/editor-sidebar/related-posts/hooks.ts (3)

59-59: Ensure the context: 'view' parameter is correctly implemented in getEntityRecords for user entities.

---

69-69: Ensure the context: 'view' parameter is correctly implemented in getEntityRecords for category entities.

---

79-79: Ensure the context: 'view' parameter is correctly implemented in getEntityRecords for post_tag entities.

README.md (1)

3-3: Updated stable tag to 3.14.5 to reflect the new version.

src/content-helper/editor-sidebar/related-posts/component.tsx (2)

297-297: Added condition to check if the author is unavailable in the related posts panel.

---

312-313: Ensure the new condition for unavailable authors correctly updates the filter settings.

CHANGELOG.md (1)

8-13: The changelog entry for version 3.14.5 correctly documents the bug fix related to non-admin users and the PCH Related Posts filters. This aligns with the PR objectives and the AI-generated summary.