[Fastlane.Swift] Unusable for CI builds

[pchmelar]

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

When Fastlane.swift fails with some error, the exit code is 0 instead of 1. Because of that, it is basically unusable for CI builds, as the job fails, but a pipeline doesn't stop.

This issue is already described in #21849 and resolved in #20563 - can we please merge it? 🙏

Sorry for the duplicate issue, but I'm desperate to make this work and don't know how else to contact the maintainers. 😓

[rasberik]

but I'm desperate to make this work

Its hard to get PRs merged here probably due to overwhelming amount of open Issues and PRs, and maintainers mostly work on what they are interested in themselves.

For instant solution, I recommend you to fork fastlane repository, create a release branch where you cherry pick the commits/PRs you need and create own tagged releases on that branch. Your codebase will need to redirect to fork repo.

If you find a way to reach to maintainers - let me know too 😇