Repository navigation
Adopt superseded histories and enforce shared session-owned locks - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow explicit retirement of superseded legacy identities while preserving the canonical migration version and history. The status command prints the exact legacy keys and adoption command. Expected operational failures have a dedicated exception; unexpected PHP errors stop bulk migration and retain their trace.
Use a shared database migration lock across plugins and table prefixes, check session ownership before and after execution, expose lock timeouts, and reject keys longer than the 191-byte database column.
Validation: full QA, 79 tests / 514 assertions; real MariaDB 11.8 and MySQL 8.4, 9 tests / 98 assertions each, including connection replacement and contention. No skips. Connection loss during the database client's internal SQL replay is explicitly reported as requiring reconciliation.