[codex] Cover schema target drift for triggers and indexes#147
Merged
Conversation
Merged
adamziel
added a commit
that referenced
this pull request
May 16, 2026
## Release `v0.1.18` Version bump and release metadata update for `v0.1.18`. **Changelog draft:** * Update merge reliability release evidence ([#145](#145)) * Cover schema target SQL drift revalidation ([#146](#146)) * Cover schema target drift for triggers and indexes ([#147](#147)) * Cover root-escaping filesystem symlink conflicts ([#148](#148)) * Cover usermeta behind explicit user ID imports ([#149](#149)) **Full changelog:** v0.1.17...release/v0.1.18 ## Next steps 1. **Review** the changes in this pull request. 2. **Push** any additional edits to this branch (`release/v0.1.18`). 3. **Merge** this pull request to publish `v0.1.18`. Merging will automatically build ForkPress binaries, create a GitHub release, and update the Homebrew formula.
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
1 participant
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.
What
needs-action, record current target SQL evidence, and stay conservativelyunclassified.Why
The implementation handles schema source/target drift for indexes, views, and triggers, but focused coverage only proved the target-side view case. This closes that evidence gap while preserving the conservative review model for schema conflicts.
Testing
php -l tests/cow/schema_review.phpgit diff --checkmake test-cow-schema-review(115 assertions)npm run build