0.3.2

Add Sendable conformance to most things, to make the client play better in Swift Concurrency contexts

0.3.1

Mainly documentation improvements, and extremely basic alpha Webhook API support. Some small bugs in TestAnalytics fixed as well.

Full Changelog: 0.3.0...0.3.1

0.3.0

Breaking Changes

• Tokens are loaded entirely differently now, in order to support single clients that can reach multiple Buildkite APIs. See the new initializer for BuildkiteClient.

What's New

• TokenProviders can be used to load authentication tokens dynamically as well as statically. (#4)
• Alpha support for the Agent and Test Analytics APIs
• Compatibility with Xcode 14 beta 1
• Groundwork laid for more comprehensive examples

Full Changelog: 0.2.0...0.3.0

0.2.0

• Add support for async/await
• Remove support for iOS 10-12, macOS 10.12-10.15, watchOS 3-5, and tvOS 10-12.
• Remove support for Swift <=5.5.2
• Add Followable references for ease of API consumption
• Add DocC documentation
• Add swift-format

Full Changelog: 0.1.0...0.2.0

0.1.0

This is the first minor-version release of this package. While not yet committing to the stability guarantees of a a major version, this marks a period of considered stability before making changes to the API.

This release includes a small change to the data type returned by the GraphQL resource. After some research and discussion with members of the Buildkite team, it was determined that the GraphQL API offered by Buildkite is not capable of responding with data and errors simultaneously as is outlined in the specification. This means that you can write code that maps on the variant returned by GraphQL.Content, which works well with either the Combine API or the Result returned by the closure API.

Odds and Ends

This release makes a couple of breaking changes:

• Buildkite (the client class) has been renamed to BuildkiteClient to remove confusion and also work around an LLDB bug
• Proper handling of 204 No Content responses was introduced, because I neglected it originally. These responses are now treated appropriately as successful.
• GraphQL.Content no longer must be Encodable, making the requirements for being a GraphQL response less onerous.

This release also fixes a bug with Team.Resources.List where the Everyone team has no description nor creator.

Finally, the package is published on the Buildkite docs now! Hooray!

Slightly more polished GraphQL support

0.0.4

Corrected some syntax errors in my example code

Initial GraphQL Support

You can now use the GraphQL resource to send a raw GraphQL query string and variables to the v1 endpoint. Future iterations will make this more configurable and type-safe at query-time. Heterogenous JSON values are now better expressed by the API as well.

Teams

You can now send the Team.Resources.List resource, which I forgot about while writing the initial version.

Initial release

This is the initial release! It supports all endpoints and all features in the publicly documented API site. It may still be a bit buggy.