Changelog

Version History #

The loaded plugin changelog file defines the project changelog structure as:

• Version
• optional date, only when present in repository sources
• optional categories: Added / Changed / Fixed / Security
• upgrade notes, only when code-backed

The same source also states that dates are included only when present in repository sources. In the loaded plugin changelog material, no release date is provided for the current documented plugin version, so this page does not add one.

Current Documented Plugin Version #

The loaded plugin files document the current plugin version as 1.0.1. The changelog file states that, as of 1.0.1, both the plugin header and the runtime version constant are set to 1.0.1. The overview and developer reference confirm the same version value in the plugin bootstrap metadata.

1.0.1 #

The loaded changelog file documents these code-backed facts for version 1.0.1.

Added #

As of 1.0.1, the plugin defines REST route registration for these feature areas under namespace davix-h2i/v1:

• Image
• H2I
• Tools
• Logs

The overview and behavior files confirm the same implemented REST surface for the current plugin codebase.

Changed #

As of 1.0.1, activation behavior is limited to ensuring the API key option exists and is stored with autoload disabled. The changelog file explicitly describes this as the current activation behavior for this release state.

The admin-operations file confirms the same exact activation scope:

• if davix_h2i_api_key does not exist, it is created with an empty value and autoload disabled
• if it already exists, it is rewritten with autoload disabled
• no schema migration, custom tables, cron registration, or filesystem initialization are performed during activation

Fixed #

No separate code-backed Fixed entries are provided in the loaded plugin changelog file for 1.0.1.

Security #

No separate code-backed Security section is listed in the loaded plugin changelog file for 1.0.1.

WordPress Plugin Updates #

The loaded changelog material does not provide a multi-version historical release list for the plugin. It documents the current audited code state for 1.0.1 and explicitly notes that this section reflects the current 1.0.1 repository state.

That means the public plugin changelog page should not invent older plugin releases, release dates, or category breakdowns that are not present in the loaded source files.

Backward Compatibility Notes #

The loaded changelog file includes these code-backed backward-compatibility notes for the plugin.

Uninstall Behavior #

Uninstall removes plugin option keys and attempts cleanup of plugin log file and directory paths under uploads, as implemented in uninstall.php.

The admin-operations file gives the exact options deleted on uninstall:

• davix_h2i_api_key
• davix_h2i_auth_mode
• davix_h2i_idempotency_enabled
• davix_h2i_idempotency_header
• davix_h2i_timeout
• davix_h2i_retry_count
• davix_h2i_h2i_max_payload_kb
• davix_h2i_image_defaults
• davix_h2i_image_output
• davix_h2i_auto_optimize
• davix_h2i_h2i_defaults
• davix_h2i_h2i_output
• davix_h2i_tools_defaults
• davix_h2i_log_enabled

Filesystem cleanup attempted on uninstall is best-effort and conditional. Non-empty directories can remain.

Attachment Meta Is Not Removed on Uninstall #

The changelog file explicitly notes that attachment meta keys used at runtime are not removed by uninstall.php, including:

• _davix_h2i_generated
• _davix_h2i_auto_optimized

The admin-operations and security/privacy files confirm the same uninstall limitation.

No Deactivation Hook #

The changelog file states that no deactivation hook is registered in the current code. The admin-operations and overview files confirm that register_deactivation_hook is not present in the plugin PHP files.

No Option Migration Routine #

The changelog file notes that no option migration routine is defined in current code and that behavior appears to rely on existing option keys plus sanitization and default getters.

This means the loaded plugin docs do not support claims about migration wizards, schema upgrade routines, or automatic historical option transforms.

Upgrade Notes #

The loaded plugin changelog supports these upgrade notes.

Activation Remains Minimal #

Upgrading into the documented 1.0.1 code state does not introduce a documented schema migration or plugin-managed data migration. Activation behavior remains limited to API-key option autoload normalization.

Uninstall Cleanup Is Partial, Not Total #

While uninstall removes plugin options and attempts log-path cleanup, it does not remove runtime attachment meta markers such as _davix_h2i_generated and _davix_h2i_auto_optimized.

Logging Cleanup Differs from Uninstall Cleanup #

The troubleshooting and admin-operations docs document that disabling logging removes plugin log files, while uninstall attempts broader option removal and best-effort directory cleanup. These are separate lifecycle behaviors and should not be described as identical.

Historical Diff Verification Note #

The loaded changelog file includes an explicit audit note: the 1.0.1 changelog section documents the current 1.0.1 repository code state.

For public documentation, the safe source-backed statement is that this changelog page reflects the current documented plugin release state present in the loaded files, not a reconstructed release history beyond what those files explicitly provide.