v0.3.3

• Fix: Dashboard → Updates reported "Compatibility with WordPress 7.1.3: Not tested". The plugin
  is now declared tested up to WordPress 7.1, and the updater reports that as the newest point
  release of the 7.1 branch the site knows of — the running version, or a core update on offer —
  the way WordPress.org treats a declared major. (WordPress compares the value against full
  versions, so a bare 7.1 would still have read "Not tested" on 7.1.3.)
• Fix: the updater described an update using the installed copy's "Requires PHP", "Requires at
  least" and "Tested up to" instead of the release's. They are now read from the release tag (one
  small extra request, cached with the release), falling back to the installed values if that fetch
  fails — retried after 30 minutes rather than 6 hours — so an update is never withheld. WordPress
  uses an update's "Requires PHP" to keep it from being offered or auto-installed on a too-old PHP,
  so a release that raises it can no longer reach sites it would break.
• Fix: WordPress's plugin auto-updater ignores an update's "Requires at least" (it checks only PHP),
  so the updater now stops an automatic update onto a WordPress older than the release
  supports. Manual updates were already blocked by WordPress in that case.
• Change: Dashboard → Updates → Check again now also refreshes the updater's own release cache,
  so a newly published release shows up immediately instead of within 6 hours.
• Note: the update to 0.3.3 is still described by the previously installed updater, so it shows
  "Not tested" one last time; updates after it show the correct status.

What's Changed

• 0.3.3: fix "Not tested" on WordPress 7.1; updater reports the release's own requirements by @uddhabh in #4

Full Changelog: v0.3.2...v0.3.3