-
Notifications
You must be signed in to change notification settings - Fork 33
Update version number and changelog for 3.16.4 release #2725
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.4 release #2725
Conversation
WalkthroughWalkthroughThe recent updates primarily focus on incrementing the version number of the Parse.ly plugin from Changes
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this 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
Files ignored due to path filters (1)
package-lock.json
is excluded by!**/package-lock.json
Files selected for processing (6)
- CHANGELOG.md (1 hunks)
- README.md (1 hunks)
- package.json (1 hunks)
- src/class-permissions.php (2 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
Additional context used
Path-based instructions (1)
src/class-permissions.php (1)
Pattern
**/*.{html,php}
: "Perform a detailed review of the provided code with following key aspects in mind:
- Review the HTML and PHP code to ensure it is well-structured and adheres to best practices.
- Ensure the code follows WordPress coding standards and is well-documented.
- Confirm the code is secure and free from vulnerabilities.
- Optimize the code for performance, removing any unnecessary elements.
- Validate comments for accuracy, currency, and adherence to WordPress coding standards.
- Ensure each line comment concludes with a period.
- Verify code compatibility with the latest version of WordPress, avoiding deprecated functions or features."
Additional comments not posted (4)
src/class-permissions.php (4)
84-85
: Update the parameter documentation.The parameter
$current_user_can_use_pch_feature
can now benull
, indicating that the filter might not be in use. Ensure that the documentation reflects this change accurately.
Line range hint
137-150
: Integration with updated method is correct.The
get_pch_permissions_json
function correctly integrates with the updatedcurrent_user_can_use_pch_feature
method.
Line range hint
164-183
: Permissions settings array construction is correct.The
build_pch_permissions_settings_array
function correctly constructs the permissions settings array.
98-106
: LGTM! But verify the function usage in the codebase.The restructuring to prioritize the filter's output is approved.
However, ensure that all function calls to
current_user_can_use_pch_feature
are compatible with the new parameter type.Run the following script to verify the function usage:
Verification successful
Function Usage Verified: Compatible with New Parameter Type
The calls to
current_user_can_use_pch_feature
are compatible with the expected parameter types. The function is used with string arguments for the feature name and likely array arguments for options, consistent with the function's definition.
- Files and Lines:
src/content-helper/editor-sidebar/smart-linking/class-smart-linking.php
src/content-helper/excerpt-generator/class-excerpt-generator.php
src/Endpoints/content-suggestions/class-suggest-headline-api-proxy.php
src/Endpoints/content-helper/class-smart-linking-endpoint.php
src/Endpoints/content-suggestions/class-suggest-brief-api-proxy.php
src/Endpoints/content-suggestions/class-suggest-linked-reference-api-proxy.php
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all function calls to `current_user_can_use_pch_feature` are compatible with the new parameter type. # Test: Search for the function usage. Expect: Compatible with the new parameter type. rg --type php -A 5 $'current_user_can_use_pch_feature'Length of output: 5810
Script:
#!/bin/bash # Verify the types of parameters passed to `current_user_can_use_pch_feature` in the codebase. # Check the function definition for expected parameter types. ast-grep --lang php --pattern $'function current_user_can_use_pch_feature( string $feature_name, $_, $_ = false ) { $$$ }' # Verify the types of arguments passed in each usage. rg --type php $'Permissions::current_user_can_use_pch_feature' -A 3 | grep -E 'smart_linking|excerpt_suggestions|title_suggestions'Length of output: 1031
This PR updates the plugin's version number and changelog in preparation for the 3.16.4 release.
Fixed
Dependency Updates
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
CHANGELOG.md
to include version 3.16.4 changes and dependency updates.README.md
andpackage.json
to reflect 3.16.4.Style