New release - javiercasares/wpvulnerability GitHub Wiki

This is the process to check when doing a new release:

• Create a new branch, please.
• Do some coding.
• Update everything (WordPress, PHP, WP-CLI), and validate the versions
  • Be sure everything is unix find ./ -type f \( -name "*.php" -o -name "*.css" \) -exec dos2unix {} \;
• Test with WordPress Coding Standards
  • phpcs56 .
  • wpphpcs .
  • wpphpcbf .
• Plugin Check (PCP)
• Add the changes to the changelog.txt and readme.txt
• Update versions at wpvulnerability.php
• Update the Tested up to, Stable tag, Version, and last vulnerability version.
• (WordPress Simple) Test some pages / functionalities :
  • WP-Admin Dashboard widget (Dashboard)
  • Core updates (Dashboard → Updates)
  • Menu counters (Dashboard Menu)
  • Plugin list (Dashboard → Plugins)
  • Plugin vulnerable list (Dashboard → Plugins → Vulnerabilities)
  • Site Health (Dashboard → Tools → Site Health)
  • Configuration (Dashboard → Settings → WPVulnerability)
    • Save email
    • Save settings
    • Reload data
    • Test email
    • Check statistics / Contributors
  • REST API endpoints
  • WP-CLI commands
• (WordPress Multisite) Test some pages / functionalities :
  • WP-Admin Dashboard widget (Dashboard)
  • Core updates (Dashboard → Updates)
  • Menu counters (Dashboard Menu)
  • Theme list (Dashboard → Themes)
    • Theme vulnerable list (Dashboard → Themes → Vulnerabilities)
  • Plugin list (Dashboard → Plugins)
    • Plugin vulnerable list (Dashboard → Plugins → Vulnerabilities)
  • Site Health (Dashboard → Tools → Site Health)
  • Configuration (Dashboard → Settings → WPVulnerability)
    • Save email
    • Save settings
    • Reload data
    • Test email
    • Check statistics / Contributors
  • REST API endpoints
  • WP-CLI commands
• Update the POT file
• Create a Draft PR
• Validate the SonarCloud Code Review
• Publish the PR
• Approve the PR
• Create the ZIP file
• Publish a new version