Skip to content

Force Danger library product to be dynamic so libDanger is always found - #669

Draft
f-meloni with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-danger-swift-xcode-compatibility
Draft

f-meloni with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-danger-swift-xcode-compatibility

Conversation

Copilot AI commented Oct 3, 2026 •

Copy link
Copy Markdown

With Xcode 27, danger-swift fails with Could not find a libDanger to link against. The runner only accepts a folder containing libDanger.dylib or libDanger.so. I could not test on Xcode 27, so the cause below is a hypothesis.

  • Package.swift
    • The Danger product had no explicit type, so SwiftPM picks it. I suspect the newer toolchain now builds it as a static library, which the runner's lookup would not find.
    • The product is now declared .dynamic, so libDanger.dylib or libDanger.so is always emitted:
.library(name: "Danger", type: .dynamic, targets: ["Danger"]),

For review

  • Please verify on Xcode 27 that a release build now produces libDanger.dylib.
  • If the error persists, check whether Scripts/install.sh copies the library into lib/danger. It only copies a fixed list of file names.

Co-authored-by: f-meloni <17830956+f-meloni@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix Danger-Swift v3.2.23.0 not working with Xcode 27.0 in Gitlab CI Force Danger library product to be dynamic so libDanger is always found Oct 3, 2026
Copilot AI requested a review from f-meloni October 3, 2026 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Danger-Swift v3.23.0 not working with Xcode 27.0 in Gitlab CI

2 participants