Updates & Compatibility: Where Release Info Comes From

1. Where Release Info Lives (Per Your Readmes) #

Your readme.txt and readme.md are the main human-facing sources of release information:

• They include:
  • Plugin name, description, tags.
  • Minimum PHP/WordPress requirements.
  • List of features (modules) and Free vs Pro sections.
  • A “Changelog” section that lists versioned changes (see next article).
• These readmes are also what WordPress.org (or your marketplace) uses to build:
  • The plugin page.
  • The “Changelog” tab.

image IMAGE PLACEHOLDER: Screenshot of your readme.txt open in a code editor, with sections for Description, Features, Installation, FAQ, and Changelog. IMAGE image

2. Version & Compatibility Fields #

The readme and plugin header expose version and compatibility info:

• Version – current plugin version (e.g., 1.0.0, 1.1.0, etc., as you maintain it).
• Requires at least – minimal WordPress version.
• Tested up to – latest WordPress version you’ve tested against.
• Requires PHP – minimal supported PHP version.

Your docs assume that:

• Users should check these fields before updating, especially on older WordPress/PHP setups.

3. How Updates Reach the Site (From Docs Perspective) #

While the docs don’t re-implement WordPress core behavior, they assume:

• Davix AI Engine is installed like any WordPress plugin.
• Updates come via:
  • WordPress’ plugin update mechanism (zip or repository).
  • Freemius-powered auto-updates for Pro (based on license).

In your documentation page, you should explain:

1. How users know a new version is available (WordPress update notices).
2. That they can read the Changelog (next article) to see what changed.
3. That Pro features will continue to work after update as long as:
   • Their license remains active.
   • Their environment meets the version requirements.