Repository navigation
fix(gamedata): accept the unversioned decay tag - #5
Merged
Merged
Conversation
Co-Authored-By: Codex <codex@openai.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.
GoldSrc_VibeSignatures v20261024a adds the unversioned
decayidentity. The synchronizer validates the complete upstream index before selecting manifest entries, so the old versioned-only rule rejects the release even when this component does not consume Decay.Explicitly accept
decayalongside the existing versioned tags and keep rejecting unknown unversioned or malformed tags. Add regression coverage for stable/content-addressed snapshot names and every manifest version-condition field.The component manifest and its selected game versions are unchanged.
Validation:
--validate-only.git diff --checkpassed. No native code changed; native builds and in-game behavior were not tested.