-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SwiftLint update strategy #562
Comments
I'd love to see this fixed too. Maybe some workaround to allow pointing to a custom swiftlint binary, so that we don't have to require a new Danger Swift release. Or some other way. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the latest
danger-swift-with-swiftlint
Docker image is using SwiftLint 0.48.0 which was released in July 2022, so it's a couple of versions behind. This introduces some issues:As far as I understand, bumping the SwiftLint version would require a new Danger Swift release. Would this alone be a good enough reason for a new release? If so, are we encouraged to do it?
The text was updated successfully, but these errors were encountered: