chore: bump version to 0.1.4 (#33) #34
Merged
Annotations
7 warnings
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, nick-fields/retry@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run wordpress/plugin-check-action@v1
Failed to post/update comment: Failed to create comment: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run wordpress/plugin-check-action@v1:
src/Routing/FeedEndpoint.php#L1
The "feedwright/sub" prefix is not a valid namespace/function/class/variable/constant prefix in PHP.
|
|
Run wordpress/plugin-check-action@v1:
src/Routing/FeedEndpoint.php#L1
The "feedwright/binding" prefix is not a valid namespace/function/class/variable/constant prefix in PHP.
|
|
Run wordpress/plugin-check-action@v1:
src/Query/ArgsBuilder.php#L153
Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.
|
|
Run wordpress/plugin-check-action@v1:
src/Query/ArgsBuilder.php#L75
Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.
|
|
Run wordpress/plugin-check-action@v1:
src/Plugin.php#L96
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
|
Loading