error: no tests found; create a target in the 'Tests' directory

Seems super strange

I believe is because of 8ae3636
I've reverted it, so if you pull master it should work now

@f-meloni didn't seem to fix it 🤔

@AvdLee that commit is still in your branch, you will probably have to make an interactive rebase :(

Can you please update the changelog if you don't mind?

There's a Danger rule for that, did you know? 😜
On a serious note; maybe you like this?
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

I'll add it now at least!

To be fair I can test it in master as well, no reason to hold this PR

Can you please update the changelog if you don't mind?

There's a Danger rule for that, did you know? 😜 On a serious note; maybe you like this? https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

I'll add it now at least!

I think we are linking the changelog on Twitter when we make a release (which automatically adds the new version to the changelog blow the ## Master), if there is a way to automatically generate the release with an API, we might maybe point directly to the release, but would be generated after the tag is pushed, and so when I think the twitter hook is already been executed, and the tweet already created 🤔
cc. @orta

I've tried to do a make install (after I deleted the previous files in /usr/lib/danger, like brew would do, and if I run Danger at the moment I get

ERROR: Could not find a libDanger to link against at any of: [".build/debug", ".build/x86_64-unknown-linux/debug", ".build/release", "/usr/local/lib/danger", "/opt/homebrew/lib/danger"]
Or via Homebrew, or Marathon

because there is no library to copy in the .build.
It works only if you are using SPM in the project (and in that case works also if you install it via brew, because builds the framework with SPM)

I've reproduced the issue here https://github.com/danger/swift/runs/4055493568?check_suite_focus=true and added a CI suite that can reproduce the issue

@f-meloni is there a middle ground you think that fixes the Xcode 13 bug ánd doesn't break old systems?
As a last resort we could keep using our own fork, but that's obviously not ideal!

@AvdLee I would love to find something like a parameter that I can pass to swift build to force it to build Danger as dynamic without having to specify it on SPM.
If that doesn't work then the only other solution I can think of is changing the Package.swift from the install script before installing

If that doesn't work then the only other solution I can think of is changing the Package.swift from the install script before installing

If it's only failing for that script, it would make total sense. It would be weird to me to not support SPM which is heavily used in Danger environments, so we need to get to a working solution. This sounds like the way to go to me!