1.6.0

Spring cleaning!

• Using Updated TrailerQL and TrailerJson for improved performance and stability.
• Refactored to Swift 6.0 to eliminate potential data races and be more efficient.
• Will report GraphQL queries that result in an error if verbose logging is requested.

(Linux static binaries coming soon)

Version 1.5.2

Fixes for handling item relationships, such as labels and milestones.

Version 1.5.0

• Another cleanup / keeping-current pass, fixing some threading issues and tracking some GH API changes for PRs.
• Added -max-node-cost parameter to help tune querying:

-max-node-cost: Maximum GraphQL node cost per query. If you get errors about 
                queries failing, reduce this to a lower value. The theoretical 
                maximum is 500000 but in practise this should be much lower. 
                The default is 10000. 

macOS versions prior to 10.14.4 require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

The Windows binary "works on my machine", and was built with the latest Swift toolchain in Windows 11. If you encounter issues with it please raise an issue. If you get an error about VCRUNTIME140.DLL missing, please install it from here.

1.4.0

• A spring cleaning update that dusts off the codebase, uses faster network IO on macOS and Linux, as as well bringing quite a few GraphQL parsing optimisations from the main Trailer project.

macOS versions prior to 10.14.4 require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

The Windows binary "works on my machine", and was built with the latest Swift toolchain in Windows 11. If you encounter issues with it please raise an issue. If you get an error about VCRUNTIME140.DLL missing, please install it from here.

Version 1.2.0

• New option -dryrun performs all operations but does not save the result
• Support for “check run” based statuses
• Minor performance improvements
• Minor copy and bug fixes

macOS versions prior to 10.14.4 require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

The Windows binary "works on my machine", and was built with the latest Swift toolchain in Windows 10. If you encounter issues with it please raise an issue. If you get an error about VCRUNTIME140.DLL missing, please install it from here.

Version 1.1.2

• Fix to allow mixed-case auth tokens to be stored via trailer -token
• Stores auth token file with improved permissions for security (many thanks to @afh)

macOS versions prior to 10.14.4 require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

The Windows binary "works on my machine", and was built with the latest Swift toolchain in Windows 10. If you encounter issues with it please raise an issue.

Version 1.1.1

• Workaround for GraphQL responses that could lead to multiple trailer run-throughs needed to fully sync.
• Compiled with the latest Swift version for performance and size improvements.
• Many thanks to @akamch for a Linux build fix

macOS versions before 10.14.4 require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

The Windows binary "works on my machine", and was built with the latest Swift toolchain in Windows 10. If you encounter issues with it please raise an issue.

Version 1.1.0

Option to sort items when listing PRs and Issues.

Example: trailer list items -sort author,updated
Field: type, number, title, repo, branch, author, created, updated

This binary requires macOS 10.14.4 and higher - previous macOS versions require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

Version 1.0.9

Built with Swift 5 and Xcode 10.2 for performance and size reduction.

This binary requires macOS 10.14.4 and higher - previous macOS versions require the Swift 5 Runtime Support for Command Line Tools package to be installed in order to run this binary.

Version 1.0.8

• Corrects an issue when the -from parameter was used, that would wipe reactions for comments which were not touched by that sync.
• Matching renamed API field requestedReviewer instead of reviewer for review request objects.