Carthage

GET https://watchchangelog.com/api/v1/entries?source=carthage.releases

{
  "source": "carthage.releases",
  "vendor": "Carthage",
  "id": "tag:github.com,2008:Repository/25050844/0.40.0",
  "published_at": "2024-09-09T14:53:24.000Z",
  "title": "0.40.0",
  "url": "https://github.com/Carthage/Carthage/releases/tag/0.40.0",
  "summary": "Changes Under all Xcodes and xcodebuild s — Carthage will pass SUPPORTS_MACCATALYST=NO just before CARTHAGE=YES . We consider adding that passed/hardcoded build setting safe — considering any likelihood ‘build setting chaining/interpolation’ using SUPPORTS_MACCATALYST is guessed to be almost entirely non-existent. Please file an issue if unexpected effects are seen. Under all Xcode versions, all xcodebuild invocations of -showBuildSettings that return non-0 exit code and standardError matching error[:] [^\\n]*Found no destinations for the scheme [^\\n]+ and action [^\\n]+[.]\\n will see non-surfacing of those errors. Carthage proceeds as if that xcodebuild invocation never happened (which is essentially how Carthage behaved before it had one more non-0 exit code return to deal with.) No longer (under Xcode 16 and above) prefix -showBuildSettings with solely the archive action. Carthage has long-standingly built simulator code under the build action. Xcode Build Setting OBJROOT now appears to have more path components. We lop some path components off (only under Xcode 16 and above.) Acknowledgements Thank you to @prassyy for a pull request!",
  "tags": [
    "Carthage",
    "carthage.releases",
    "package-manager",
    "ios",
    "swift"
  ]
}