Stabilize cross-platform conformance hashes - #75
Merged
Conversation
jcwal1516
had a problem deploying
to
crates-io-publish
August 7, 2026 03:45 — with 
GitHub Actions
Failure
GitHub Actions
Failure
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.
Summary\n- force LF checkouts for versioned T.803 TOML evidence inputs\n- add a repository-policy regression test for all five conformance manifests\n\n## Root cause\nThe Windows CPU report's ICS hash matched the committed LF file after CRLF conversion exactly, so exact-SHA verification correctly rejected the cross-platform mismatch.\n\n## Validation\n- cargo test -p xtask --test repo_lint j2k_conformance_manifests_have_platform_stable_line_endings\n- cargo xtask ci