Update swift-log library - #44
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d6cd4faef
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .package(url: "https://github.com/slidoapp/SwiftKeychain.git", .upToNextMinor(from: "2.1.0")), | ||
| .package(url: "https://github.com/groue/Semaphore.git", .upToNextMinor(from: "0.1.0")), | ||
| .package(url: "https://github.com/apple/swift-log.git", .upToNextMinor(from: "1.6.4")) | ||
| .package(url: "https://github.com/apple/swift-log.git", .upToNextMajor(from: "1.14.0")) |
There was a problem hiding this comment.
Keep swift-log compatible with the declared toolchain
When this package is resolved with the repo's declared Swift 5.5 toolchain (Package.swift says swift-tools-version:5.5 and .swift-version is 5.5.3), this new lower bound selects swift-log 1.14.0, whose manifest declares swift-tools-version:6.2. SwiftPM cannot load a dependency manifest that requires a newer tools version than the running toolchain, so users/builds still using the advertised 5.5 toolchain will fail during package resolution before compiling. Either cap/select a swift-log release that supports Swift 5.5 or update this package's declared toolchain requirements consistently.
Useful? React with 👍 / 👎.
upToNextMinortoupToNextMajorfor better compatibility