Once we drop support for upgrading directly from v1.0.x, remove the migration scaffolding that lives in this codebase as @deprecated 1.1.0.
Search for @deprecated 1.1.0 across the repo — every hit is fair game for deletion. Roughly: the v3 → v4 CPT-rename migration step, the legacy slug constants, the import back-compat remap, and the legacy entries in the uninstall cleanup list.
Keep the activation-hook get_option guard in opentrust.php — that's a general migration pattern, not v4-specific.
Introduced by PR #21 / issue #20.
Once we drop support for upgrading directly from v1.0.x, remove the migration scaffolding that lives in this codebase as
@deprecated 1.1.0.Search for
@deprecated 1.1.0across the repo — every hit is fair game for deletion. Roughly: the v3 → v4 CPT-rename migration step, the legacy slug constants, the import back-compat remap, and the legacy entries in the uninstall cleanup list.Keep the activation-hook
get_optionguard inopentrust.php— that's a general migration pattern, not v4-specific.Introduced by PR #21 / issue #20.