The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.
This release removes the check from `Command.init(executablePath:)` that looks if there is an executable file at the given path.
Apparently `Foundation.FileManager.isExecutableFile(atPath:)` can have false negatives, in which case it would be impossible to initialize `Command` with a custom executable file, as the initializer would always throw an error.
Thanks to @hisaac for pointing this out to me and for implementing the fix.
Furthermore, `ChildProcess`es that have both a piped stout and stderr now have a property `mergedOutputLines` that allows you to get the stderr and stdout output of a process in one async sequence.
This release adds access to the native async sequences from `Foundation` wherever they're `@available`.
This release adds some API for accessing the stdout/stderr of a process as `Data` instead of as a `String`. It also makes it possible to access the signal that the process was terminated with on Linux and macOS.
Additionally, this release contains a simple fix by @doozMen, that allows the package to build correctly again on Linux.
Version 1.1.2 adds initial support for Windows.
This means, that the package builds now on Windows and that a few little test programs executed correctly.
However, it doesn't mean that all features are thoroughly tested on Windows as they are on macOS/Linux. This is partly due to the fact that Windows doesn't have executables called `echo.exe` or `cat.exe`, which would be needed for the tests to run at all. If someone wants to help getting the support for Windows to a proper stage, feel free to do so, it would be highly appreciated!
This is the first version of SwiftCommand that is actually working with Swift 5.6 or 5.7 on both macOS and Linux.
Just consider the versions before this one as beta versions – I accidentally only tested them with Swift 5.7 (beta) and/or only on macOS.