Repository navigation
CI: drift avoids every content item the round touched on the sending side - #260
Merged
Merged
Conversation
…side #259 only skipped items the round edited with content/edit. A list swap saves both items it moves (new versions), and so do publishes, so drift could still pick a copy of one and grade a change on both sides (seed 799975145, round 1: list swap of Posts #112, drift on its copy #16). Drift now skips the copies of every content item named by the round's content and ordering changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Harness-only fix (
ci/permutation/run.mjs). No CLI code changes.The re-pointed
v1.3.0-beta.1tag run (run 41677294520) failed one check, so nothing was published. #259 only kept drift off items the round edited withcontent/edit. In round 1 a list swap moved Posts #112 and #124, which saves both items with new versions, and drift then edited #112's target copy (#16): a change on both sides, which the CLI correctly reported as a conflict.The fix: drift skips the receiving side's copies of every content item named by the round's content and ordering changes (edits, list swaps, publishes, deletes). Those details all name source content IDs; page and model changes don't count.
Tested: a replay of the failed run (same seed
799975145, beta tier, fresh dev instances) passed every check in all 5 rounds.After this merges,
v1.3.0-beta.1gets re-pointed at the new main commit to re-run the gated publish.🤖 Generated with Claude Code