All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project follows Semantic Versioning where applicable.
- Require explicit retirement for additional legacy adoptions without changing the canonical version; expose exact adoption diagnostics in status and reject canonical/alias version conflicts.
- Validate migration identities and plugin slugs against the 191-byte metadata storage limit before writes.
- Share advisory locks across all migration scopes in a database, configure the timeout, and verify connection/lock ownership before SQL and metadata writes.
- Continue other plugins only after typed operational failures; propagate PHP/programming errors immediately.
- Detect a failed
dbDelta()query that a later successful query would have masked, so the migration is no longer recorded as applied with missing columns or indexes. - Restrict
wp migration version --deleteto local/development environments likerollbackandexecute --down, because it makes the nextmigraterunup()again. - Pin the shared
sympress/workflowsCI workflows to v1.3.2.
- Use the Symfony 8.1.11 security patches released on November 4.
- Continue other plugins after a failed migration, then return a failing aggregate CLI result.
- Add administrator-only
wp migration adoptfor an explicitly confirmed exact legacy identity/version; retain the recorded version and append-only history without migration SQL. - Run real database contracts against pinned MySQL 8.4 and MariaDB 11.8 services.
- Document the two narrowly scoped WordPress Plugin Check exceptions for the private temporary CSV-formatting stream; WordPress file-operation checks remain enabled elsewhere.
- Grant the archive caller the permissions required by the pinned reusable workflow, with artifact attestations still explicitly disabled.
- Exclude development tests, tooling and documentation from the WordPress archive.
- Resolve deferred schema SQL under the advisory lock, recheck applied state before planning, and release the lock on planning failures.
- Add the backward-compatible deferred-operation executor contract used by ORM schema migrations.
- Block WP-CLI database rollbacks and backward migration targets outside loaded WordPress local/development environments, including missing environment APIs.
- Enforce forward-only target execution inside the manager while preserving the default library rollback API for explicitly reviewed inverse migrations.
- Correct WP-CLI execution flag synopsis so
--upand--downare recognized; the executor continues to require exactly one direction.
- Split WP-CLI migration command execution and reporting into focused collaborators.
- Adopt shared SymPress QA tooling for package scripts and development dependencies.
- Cover rollback behavior when a migration fails during reverse execution.