Skip to content

MacOS 15 dependency issue - Crash in Swiftlint 0.59.0 #12060

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

Open
1 of 15 tasks
andrewclaus opened this issue Apr 17, 2025 · 2 comments
Open
1 of 15 tasks

MacOS 15 dependency issue - Crash in Swiftlint 0.59.0 #12060

andrewclaus opened this issue Apr 17, 2025 · 2 comments

Comments

@andrewclaus
Copy link

Description

There is a crash in Swiftlint 0.59.0, see here: realm/SwiftLint#6052

This dependency was updated in the MacOS 15 image 3 days ago, which started breaking my build.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Image version and build link

20250408.1132

Is it regression?

20250331.1080

Expected behavior

Swiftlint runs without crashing

Actual behavior

Swiftlint error:

parser: expected all keys to be unique but found the following duplicated key(s):

Repro steps

Run swiftlint on your project

@ijunaidm1
Copy link
Contributor

Hi @andrewclaus - We will look into the issue and keep you posted with the updates.
Thank you.

@sangeeths03
Copy link
Contributor

Hi @andrewclaus,

I was able to successfully reproduce the issue. Starting from image version 20250408.1132, the SwiftLint version was upgraded to 0.59.0. I also tested this with 0.59.1, and both versions are crashing when the configuration .swiftlint.yml contains duplicate keys and SwiftLint is run from the root directory.It may be due to strict validation to catch duplicate keys in the newer versions/ may be a bug from their end.

In earlier image versions like 20250331.1080, the SwiftLint version was 0.58.2, and it handled the same duplicate key issue by just showing a warning — no crash. So this clearly shows it's a change in behavior from SwiftLint, not an issue with the runner itself.

Suggestion: If your config file has duplicate keys, try running SwiftLint from inside the subdirectory containing the config instead of from the root — this avoids the crash(for version 0.59.0) / avoid any duplicate keys in .swiftlint.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants