JP Simard

We’re not using BrightFuture or FileKit, so those errors are coming from something else.

I think your SwiftPM caches may be out of date. Please clear those and try again.

Version 0.9.2 is from March 2016: https://github.com/realm/SwiftLint/releases/0.9.2 Please try again with 0.50.3.

Please clear your SwiftPM caches. This StackOverflow answer has some steps to do that: https://stackoverflow.com/a/68876107/373262

I'm not interested in maintaining this plugin. It's nothing but a headache for me so far. I might remove it from the next release and folks can provide their own...

The invalid manifest issues should hopefully be fixed with https://github.com/realm/SwiftLint/pull/4674 The `Entry point (_main) undefined` issue is entirely separate. @evfemist moving the plugin from `.buildCommand` to `.prebuildCommand` seems reasonable to...

> We'd be willing to work on a PR for this but wanted to know if such a contribution would be welcome first. Certainly!

Yes this would be great, and we're already using Docker Buildx so in theory it should be possible to update our CI to run that. I tried a few months...

The Linux binaries in the release assets are generated in Docker, so that’s the first step. Unfortunately it looks like with QEMU and the default GitHub Actions machines they’re not...

> Sorry to hijack/bump. I noticed newer versions also don't have the Linux x86 binary. (We use SwiftLint in GitHub actions with the Linux runner as it's a lot cheaper...