Repository navigation
Recognize metadata layouts for unknown builds; release 0.5.8 - #19
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
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.
Unknown FM26 builds could fail during metadata reading before
infoorvalidatecould produce useful output. Metadata reading now accepts a unique structural match among the existing layouts for the same section schema. Ambiguous or malformed candidates still fail, and other readers retain their compatibility checks.Prepares patch release 0.5.8. Refs #18; 26.1.3 still needs reporter confirmation.
Validation: the full suite passed, including the local corpus. Added CLI regressions pass. Metadata selection preserves results across the available local saves. Lint, formatting, type checks, distribution checks, and isolated wheel smoke tests on Python 3.12 and 3.14 pass.
The change contains no save files, fragments, screenshots, or real player data. It reuses existing observed layouts; no decompilation, leaked material, or unlicensed parser code was used.