Skip to content

Releases: Zollerboy1/SwiftCommand

1.4.2: Enable compilation using Static Linux SDK

14 Apr 15:26
1.4.2
28efb03

Choose a tag to compare

This release adds the ability to use this package when compiling using the the Static Linux SDK.

Furthermore, there were some concurrency warnings when building this package using Swift 6. These are fixed in this release.

Version 1.4.2 also bumps the versions of the swift-system, swift-collection, and swift-async-algorithms dependencies and reimplements the test suite using Swift Testing.

1.4.1: Bump version of dependency swift-async-algorithms

23 Apr 14:01
1.4.1
4a0ea76

Choose a tag to compare

This release bumps the version of the dependency swift-async-algorithms to 1.0.0.

1.4.0

28 Jul 15:34
1.4.0
f14b106

Choose a tag to compare

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, ChildProcesses 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.

1.3.0

01 Jun 08:23
1.3.0
4c9c743

Choose a tag to compare

This release adds access to the native async sequences from Foundation wherever they're @available.

1.2.0

13 Mar 13:40
1.2.0
10a281c

Choose a tag to compare

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.

1.1.2

17 Aug 00:35
1.1.2
b4ea08c

Choose a tag to compare

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!

1.1.1

16 Aug 20:49
1.1.1
cb1bfad

Choose a tag to compare

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.