|
1 | | -**Experimental**: This is a new format for release notes. The format and availability is subject to change. |
| 1 | +## 2022.4.0 |
| 2 | +### Bug Fixes |
| 3 | +- `cloudflared tunnel run` no longer logs the Tunnel token or JSON credentials in clear text as those are the secret |
| 4 | +that allows to run the Tunnel. |
| 5 | + |
| 6 | +## 2022.3.4 |
| 7 | +### New Features |
| 8 | +- It is now possible to retrieve the credentials that allow to run a Tunnel in case you forgot/lost them. This is |
| 9 | +achievable with: `cloudflared tunnel token --cred-file /path/to/file.json TUNNEL`. This new feature only works for |
| 10 | +Tunnels created with cloudflared version 2022.3.0 or more recent. |
| 11 | + |
| 12 | +### Bug Fixes |
| 13 | +- `cloudflared service install` now starts the underlying agent service on Linux operating system (similarly to the |
| 14 | +behaviour in Windows and MacOS). |
| 15 | + |
| 16 | +## 2022.3.3 |
| 17 | +### Bug Fixes |
| 18 | +- `cloudflared service install` now starts the underlying agent service on Windows operating system (similarly to the |
| 19 | +behaviour in MacOS). |
| 20 | + |
| 21 | +## 2022.3.1 |
| 22 | +### Bug Fixes |
| 23 | +- Various fixes to the reliability of `quic` protocol, including an edge case that could lead to cloudflared crashing. |
| 24 | + |
| 25 | +## 2022.3.0 |
| 26 | +### New Features |
| 27 | +- It is now possible to configure Ingress Rules to point to an origin served by unix socket with either HTTP or HTTPS. |
| 28 | +If the origin starts with `unix:/` then we assume HTTP (existing behavior). Otherwise, the origin can start with |
| 29 | +`unix+tls:/` for HTTPS. |
| 30 | + |
| 31 | +## 2022.2.1 |
| 32 | +### New Features |
| 33 | +- This project now has a new LICENSE that is more compliant with open source purposes. |
| 34 | + |
| 35 | +### Bug Fixes |
| 36 | +- Various fixes to the reliability of `quic` protocol. |
| 37 | + |
| 38 | +## 2022.1.3 |
| 39 | +### New Features |
| 40 | +- New `cloudflared tunnel vnet` commands to allow for private routing to be virtualized. This means that the same CIDR |
| 41 | +can now be used to point to two different Tunnels with `cloudflared tunnel route ip` command. More information will be |
| 42 | +made available on blog.cloudflare.com and developers.cloudflare.com/cloudflare-one once the feature is globally available. |
| 43 | + |
| 44 | +### Bug Fixes |
| 45 | +- Correctly handle proxying UDP datagrams with no payload. |
| 46 | +- Bug fix for origins that use Server-Sent Events (SSE). |
| 47 | + |
| 48 | +## 2022.1.0 |
| 49 | +### Improvements |
| 50 | +- If a specific `protocol` property is defined (e.g. for `quic`), cloudflared no longer falls back to an older protocol |
| 51 | +(such as `http2`) in face of connectivity errors. This is important because some features are only supported in a specific |
| 52 | +protocol (e.g. UDP proxying only works for `quic`). Hence, if a user chooses a protocol, cloudflared now adheres to it |
| 53 | +no matter what. |
| 54 | + |
| 55 | +### Bug Fixes |
| 56 | +- Stopping cloudflared running with `quic` protocol now respects graceful shutdown. |
2 | 57 |
|
3 | 58 | ## 2021.12.2 |
4 | 59 | ### Bug Fixes |
|
0 commit comments