ci: add workflow to run wp plugin checks · pluginkollektiv/statify@be902fe

Triggered via push September 21, 2024 15:36

stklcode

pushed be902fe

ci/plugin-check

Status Failure

Total duration 2m 16s

Artifacts –

wordpress-plugin-check.yml

on: push

check

2m 8s

Annotations

3 errors and 10 warnings

outdated_tested_upto_header: readme.txt#L1

Tested up to: 6.5 < 6.6. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.

stable_tag_mismatch: readme.txt#L1

The Stable Tag in your readme file does not match the version in your main plugin file. Your Stable Tag is meant to be the stable version of your plugin, not of WordPress. For your plugin to be properly downloaded from WordPress.org, those values need to be the same. If they’re out of sync, your users won’t get the right version of your code.

check

Process completed with exit code 1.

readme_parser_warnings_too_many_tags: readme.txt#L1

One or more tags were ignored. Please limit your plugin to 5 tags.

textdomain_mismatch: statify.php#L1

The TextDomain header in the plugin file does not match the slug. Found "statify", expected "dist".

WordPress.DB.DirectDatabaseQuery.DirectQuery: inc/class-statify.php#L152

Use of a direct database call is discouraged.

WordPress.DB.DirectDatabaseQuery.DirectQuery: inc/class-statify-dashboard.php#L308

Use of a direct database call is discouraged.

WordPress.DB.DirectDatabaseQuery.NoCaching: inc/class-statify-dashboard.php#L308

Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().