Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version number and changelog for 3.16.0 release #2613

Closed
wants to merge 2 commits into from

Conversation

vaurdan
Copy link
Contributor

@vaurdan vaurdan commented Jul 8, 2024

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

Added

  • Content Helper: Implement AI feature permissions (#2604)
  • Settings page: Add "Content Helper" tab (#2554)
  • PCH Smart Linking: Add Inbound Smart Links support (#2553)
  • PCH Smart Linking: Add Smart Linking back-end (#2544)
  • PCH Smart Linking: Implement Smart Links Reviewing step (#2507)

Changed

  • PCH: Initialize Content Helper features on (#2606)
  • PCH Sidebar: Move initialization to admin_init (#2578)
  • PCH Excerpt Suggestions: Allow editing when reviewing (#2506)

Removed

  • PCH Smart Linking: Remove Link Length option from the UI (#2508)

Fixed

  • Fix some untranslatable strings (#2612)
  • PCH: Fix potential fatal with strict parameter (#2610)
  • PCH Excerpt Suggestions: Improve error handling (#2609)
  • Content Helper: Fix non-dismissible Notices (#2600)
  • ContentHelperError: Avoid double prefix in error messages (#2580)
  • PCH Sidebar: Show detailed error messages in Snackbar Notices (#2579)
  • PCH Smart Linking: Prevent duplicate Smart Links (#2571)
  • PCH Smart Linking: Prevent Smart Linking from running on Freeform (Classic) blocks (#2570)
  • PCH Smart Linking: Fix issue when processing a single block (#2547)

Dependency Updates

  • The list of all dependency updates for this release is available here.

Summary by CodeRabbit

  • New Features

    • Added AI feature permissions.
    • Introduced a "Content Helper" tab on the settings page.
    • Supported Inbound Smart Links in PCH Smart Linking.
  • Bug Fixes

    • Fixed untranslatable strings.
    • Resolved fatal errors with strict parameters.
    • Improved error handling.
    • Prevented duplicate Smart Links.
  • Chores

    • Updated version to 3.16.0 across various files.

@vaurdan vaurdan requested a review from a team as a code owner July 8, 2024 10:23
@vaurdan vaurdan added this to the 3.16.0 milestone Jul 8, 2024
@vaurdan vaurdan self-assigned this Jul 8, 2024
Copy link
Contributor

coderabbitai bot commented Jul 8, 2024

Walkthrough

Walkthrough

In version 3.16.0 of the wp-parsely project, several new features and improvements have been introduced. These include AI feature permissions, a new "Content Helper" tab, and support for Inbound Smart Links. Numerous initialization methods, sidebar settings, and error handling mechanisms have also been updated. Dependency updates and various fixes, such as handling untranslatable strings and preventing duplicate Smart Links, are incorporated as well.

Changes

Files Change Summaries
CHANGELOG.md Documented new features, initialization changes, sidebar updates, error handling improvements, and various fixes.
README.md, package.json, tests/e2e/utils.ts, wp-parsely.php Updated version from 3.15.0 to 3.16.0.
.../ContentHelperFeatures.php Changed initialization method for Content Helper features.
.../Sidebar.php Changed initialization method for sidebar.
.../ExcerptSuggestions.php Updated editing permissions.
.../SmartLinking.php Removed Link Length option from UI; prevented duplicate Smart Links and restricted Smart Linking on Freeform blocks.
.../Strings.php Fixed untranslatable strings.
.../EnqueueSettingsAssets.php Fixed potential fatal error due to strict parameters.
.../Notifications.php Improved error handling in Content Helper and sidebar notices; fixed non-dismissible notices.
.../ErrorMessages.php Adjusted error message prefix handling for ContentHelperError.

Sequence Diagram(s)

Possibly related issues

  • Parsely/wp-parsely#2611: The issue is for tracking the release of wp-parsely 3.16.0, which matches the version updated in this PR.
  • Parsely/wp-parsely#2479: Previous release process for wp-parsely 3.15.0. The process outlined in this issue can be referenced for the 3.16.0 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
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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 7db49de and b61b3d9.

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 (3)
  • package.json
  • tests/e2e/utils.ts
  • wp-parsely.php
Additional context used
LanguageTool
README.md

[typographical] ~5-~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: ....0 Requires at least: 5.2 Tested up to: 6.5 Requires PHP: 7.2 License: GPLv...

(RP_COLON)

Additional comments not posted (8)
README.md (2)

3-3: LGTM!

The version number has been correctly updated to 3.16.0.


5-5: Skip LanguageTool suggestion.

The use of colons in the context of plugin requirements is standard and clear. The flag appears to be a false positive.

Tools
LanguageTool

[typographical] ~5-~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: ....0 Requires at least: 5.2 Tested up to: 6.5 Requires PHP: 7.2 License: GPLv...

(RP_COLON)

CHANGELOG.md (6)

8-8: Verify the release date.

Ensure that the release date 2024-07-08 is correct and aligns with the planned release schedule.


10-16: LGTM! Added features are well-documented.

The added features are clearly listed with references to the respective pull requests.


18-22: LGTM! Changed features are well-documented.

The changed features are clearly listed with references to the respective pull requests.


24-26: LGTM! Removed features are well-documented.

The removed features are clearly listed with references to the respective pull requests.


28-38: LGTM! Fixed issues are well-documented.

The fixed issues are clearly listed with references to the respective pull requests.


40-42: LGTM! Dependency updates are well-documented.

The dependency updates are clearly listed with a reference to the respective pull requests.

Copy link
Collaborator

@acicovic acicovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. You can also check against previous such PRs.

@vaurdan vaurdan closed this Jul 8, 2024
@vaurdan vaurdan deleted the update/wp-parsely-version-to-3.16.0 branch July 8, 2024 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants