Repository navigation
Lint with Swift 6.4's swift-format - #110
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
The lint job used the macos-15 runner's Xcode toolchain (Swift 6.2.x), whose
swift-formatorders an@_spi(…) @testable importline differently from the 6.4 formatter the code is written with. #109 passes lint locally under 6.3 and 6.4 but fails in CI onOrderedImports.The lint job now runs in the
swift:6.4.0container;swift formatships in the toolchain. The build and test jobs are unchanged, so they still prove the 6.2.3 minimum. All ofmainalready lints clean under 6.4.CI-only; no changeset.
🤖 Generated with Claude Code