Skip to content

Releases: vyshane/grpc-swift-combine

1.0.4

09 Jul 02:00
Compare
Choose a tag to compare

Update upstream Swift gRPC to v1.2.0.

1.0.2

09 Jun 12:03
Compare
Choose a tag to compare

Update upstream Swift gRPC to v1.1.0.

1.0.1

25 Mar 12:45
Compare
Choose a tag to compare

Update CombineExt dependency to v1.3.0.

1.0.0

05 Feb 13:20
Compare
Choose a tag to compare

Update upstream Swift gRPC to v1.0.0.

0.25.0

02 Feb 11:19
Compare
Choose a tag to compare

Update Swift gRPC to v1.0.0-alpha.24. This upstream version of Swift gRPC removes previous deprecations and compatibility shims for deprecated code.

0.24.0

27 Jan 22:46
Compare
Choose a tag to compare

Update Swift gRPC to v1.0.0-alpha.23. The interface between gRPC and the generated server code has changed in upstream Swift gRPC. You will need to regenerate Swift server sources from your protobuf.

0.23.0

16 Dec 12:33
Compare
Choose a tag to compare
0.23.0 Pre-release
Pre-release

Update Swift gRPC to v1.0.0-alpha.22.

0.22.0

04 Dec 02:23
Compare
Choose a tag to compare
0.22.0 Pre-release
Pre-release

Update Swift gRPC to v1.0.0-alpha.21, which now supports watchOS. This update of Swift gRPC requires client and server code to be regenerated.

0.21.0

26 Nov 00:49
Compare
Choose a tag to compare
0.21.0 Pre-release
Pre-release

This release contains breaking API changes.

Retry Policy Improvements

This release adds a couple of improvements to the delayUntilNext callback handling when retrying failed calls.

delayUntilNext is now given the RPCError that caused the retry. This extra information can be used to apply different backoff strategies for different gRPC status codes. The new signature for delayUntilNext is (Int, RPCError) -> AnyPublisher<Void, Never>.

The library will also reset the retry count value that is given to delayUntilNext if a previous retry succeeds. This makes implementing exponential backoff easier for long running streams.

0.20.0

15 Oct 23:20
Compare
Choose a tag to compare
0.20.0 Pre-release
Pre-release

Visibility fix for RPCError properties.

Thank you for the PR @taoshotaro.