Update version number and changelog for 3.16.3 release

[vaurdan]

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

Fixed

• PCH Smart Linking: Fix issue with undefined 'wpParselySmartLinkingAllowedBlocks' (#2685)

Summary by CodeRabbit

• Bug Fixes

  • Resolved an issue related to the PCH Smart Linking feature, enhancing its functionality.

• Version Updates

  • Updated version number across the project from 3.16.2 to 3.16.3, indicating a minor release with bug fixes and improvements.

• Documentation

  • Updated CHANGELOG.md to reflect the latest fixes and improvements in the project.
  • Revised README.md with the new stable version tag.

[coderabbitai]

Walkthrough

Walkthrough

The changes introduce the release of version 3.16.3 for the Parse.ly WordPress plugin. This version primarily updates versioning information across multiple files, including the changelog, README, and various configuration files. A specific fix addresses the PCH Smart Linking feature, enhancing clarity about the latest improvements and fixes in the project.

Changes

File	Change Summary
CHANGELOG.md	Added entry for version 3.16.3, noting the fix for the undefined variable in PCH Smart Linking.
README.md	Updated stable tag from 3.16.2 to 3.16.3, without altering other metadata.
package.json	Changed version from 3.16.2 to 3.16.3, indicating a new release without functional changes.
tests/e2e/utils.ts	Updated exported constant PLUGIN_VERSION from '3.16.2' to '3.16.3'.
wp-parsely.php	Incremented plugin version in header and updated PARSELY_VERSION constant to 3.16.3.

Possibly related issues

• Release wp-parsely 3.16.3 #2686: This issue tracks the release of wp-parsely 3.16.3 and aligns with the updates made in this PR.
• Release wp-parsely 3.16.2 #2674: This is related to the previous release tracking, and the changes may help address outstanding tasks prior to this release.

---

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

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

CodeRabbit Configuration 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 ac0cd1e and 7d5ecec.

Files ignored due to path filters (1)

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

Files selected for processing (5)

• CHANGELOG.md (1 hunks)
• README.md (1 hunks)
• package.json (1 hunks)
• tests/e2e/utils.ts (1 hunks)
• wp-parsely.php (2 hunks)

Files skipped from review due to trivial changes (5)

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