oida 0.17.1 - #338
Merged
Merged
oida 0.17.1#338
Conversation
3lvis
marked this pull request as ready for review
September 17, 2026 19:00
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.
0.17 changes what a scope is measured against: an
included/excludedpattern is now relative to where the run starts rather than to the absolute path on disk, and matches through a symlinked checkout. That closes #50 properly — a pattern can no longer be written against a checkout directory name and silently match nothing somewhere else.This repository has no scoped rules, so the bump is the version and its two checksums. Lint clean,
swift buildclean.SwiftSyncandPinwheelboth carried patterns anchored with a leading/and needed a real fix; theirs land separately.