|
1 | 1 |
|
2 | 2 | # Changelog
|
3 | 3 |
|
4 |
| -## v1.19.0 - TBD |
| 4 | +## v1.20.0 - TBD |
| 5 | + |
| 6 | +## v1.19.0 - 2020-10 |
5 | 7 |
|
6 | 8 | ### Storage
|
7 | 9 |
|
8 |
| -* fix: consistent computation of XML vs. JSON endpoints |
| 10 | +* fix(storage): consistent computation of XML vs. JSON (#5095) |
| 11 | + The interaction of `ClientOptions::set_endpoint()` and the |
| 12 | + `CLOUD_STORAGE_TESTBENCH_ENDPOINT` environment variable was inconsistent |
| 13 | + across endpoints. For JSON endpoints `set_endpoint()` overrode the |
| 14 | + `CLOUD_STORAGE_TESTBENCH_ENDPOINT` value, while for XML endpoints it |
| 15 | + was the opposite. |
| 16 | + |
| 17 | + In other libraries the environment variable always wins, so we are changing |
| 18 | + the behavior here. This behavior was never documented, and it was buggy, |
| 19 | + therefore it is not a breaking change. Nonetheless, we think the bug (and |
| 20 | + the fix) is surprising enough to highlight in the CHANGELOG. |
| 21 | + |
| 22 | +* fix: enable `codecvt` (UTF-8 support for signed URLs) in MSVC (#5126) |
| 23 | +* fix(storage): avoid stalls with small reads (#5104) |
| 24 | +* feat(storage): disable XML via environment variable (#5100) |
| 25 | +* fix(storage): use correct host header (#5085) |
| 26 | + |
| 27 | +### Spanner |
| 28 | + |
| 29 | +* fix: retry gRPC operations if the connection is unexpectedly terminated (#5087) |
| 30 | +* doc(spanner): use custom retry example in the Doxygen docs (#5164) |
| 31 | + |
| 32 | +### Pub/Sub |
9 | 33 |
|
10 |
| -The interaction of `ClientOptions::set_endpoint()` and the |
11 |
| -`CLOUD_STORAGE_TESTBENCH_ENDPOINT` environment variable was inconsistent |
12 |
| -across endpoints. For JSON endpoints `set_endpoint()` overrode the |
13 |
| -`CLOUD_STORAGE_TESTBENCH_ENDPOINT` value, while for XML endpoints it |
14 |
| -was the opposite. |
| 34 | +> :warning: This library is under development and subject to breaking |
| 35 | +> changes without notice. |
15 | 36 |
|
16 |
| -In other libraries the environment variable always wins, so we are changing the |
17 |
| -behavior here. This behavior was never documented, and it was buggy, therefore |
18 |
| -it is not a breaking change. Nonetheless, we think the bug (and the fix) is |
19 |
| -surprising enough to highlight in the CHANGELOG. |
| 37 | +* feat(pubsub): wait for callback return *and* handler (#5161) |
| 38 | +* In addition, @remyabel contributed a number of examples. |
20 | 39 |
|
21 | 40 | ## v1.18.0 - 2020-09
|
22 | 41 |
|
|
0 commit comments