mirror of
https://github.com/AgentSeal/codeburn.git
synced 2026-07-30 19:36:01 +00:00
d349a01e99
Review follow-up on the Sonoma deployment-target fix: - The release minos guard was fail-open: if vtool returned nothing (missing binary, tool change) the check passed vacuously and could green-light a bad release. Now it fails closed when no minos is reported. - The libswift_errno check now excludes weak links, so it only fails on a breaking STRONG link. dyld tolerates a missing weakly-linked dylib, so a macOS 15.x SDK runner that weak-links errno at the .v14 target no longer causes a spurious release failure. - Removed em-dashes from the changed files per repo style. Verified: fresh .v14 build is minos 14.0 with no strong errno link; the guard now fails closed on an unreadable binary and passes on the real one; 71 Swift tests pass.
30 lines
1,018 B
Swift
30 lines
1,018 B
Swift
// swift-tools-version: 6.0
|
|
import PackageDescription
|
|
|
|
let package = Package(
|
|
name: "CodeBurnMenubar",
|
|
platforms: [
|
|
// macOS 14 (Sonoma) is the floor: matches Info.plist LSMinimumSystemVersion,
|
|
// the CLI install guard (MIN_MACOS_MAJOR=14), and mac/README. The earlier .v15
|
|
// bump for NSAttributedString(attachment:) was a misdiagnosis, that initializer
|
|
// is AppKit since macOS 10.0, so the binary's minos must not exclude Sonoma users.
|
|
.macOS(.v14)
|
|
],
|
|
products: [
|
|
.executable(name: "CodeBurnMenubar", targets: ["CodeBurnMenubar"])
|
|
],
|
|
targets: [
|
|
.executableTarget(
|
|
name: "CodeBurnMenubar",
|
|
path: "Sources/CodeBurnMenubar",
|
|
swiftSettings: [
|
|
.enableUpcomingFeature("StrictConcurrency")
|
|
]
|
|
),
|
|
.testTarget(
|
|
name: "CodeBurnMenubarTests",
|
|
dependencies: ["CodeBurnMenubar"],
|
|
path: "Tests/CodeBurnMenubarTests"
|
|
)
|
|
]
|
|
)
|