Repository navigation
fix: ASCII hyphens in L662 evidence notes, re-pin sha256 (unslop) - #135
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.
Main fails synapse-core tests::test_unslop_zero_em_or_en_dashes_across_workspace since #134 (23057fc) added em/en dashes in evidence/REPAIR-RECOVERY-L662. CI builds no Rust, so this was not caught.
Typographic change only: the diff is dashes only (3 em dashes, 1 en dash, replaced by ASCII hyphens). The qualification content is unchanged. This is a re-pin of final-qualification.json evidence_files hashes, not a re-measure; original bytes stay at 23057fc.
Test not weakened. Local: cargo test --locked -p synapse-core: 26 passed, 0 failed (unslop test included; it failed on main).