Repository navigation
Stabilize version fixture cleanup and clarify release attribution - #5
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.
Large temporary Git repositories can start background maintenance that races cleanup, producing an ENOTEMPTY failure on Node 22 after otherwise valid catalogue checks. Disable auto maintenance in the fixture-only Git config and use bounded filesystem cleanup retries; assertions remain unchanged. Also describe attributed source adaptations accurately in the release manifest scope.
Validation: version immutability tests passed 8/8 on Node 22.22.3; release tests passed 6/6. The deployed market passed 19 file byte comparisons and seven browser interaction groups. No template, catalogue entry or website asset changes.