chore: release v4.3.0

CHANGELOG.md

@@ -1,5 +1,15 @@
 # aspeak Changelog
 
+# v4.3.0
+
+- Add support for http and socks5 proxy. Command line option `--proxy` and environment variable `http_proxy`(or `HTTP_PROXY`) are available.
+  - Example: `aspeak --proxy "socks5://127.0.0.1:7890" text "Hello World"`
+  - You can also set the proxy in the `auth` section in your profile.
+  - By now, connection to https proxy server is not supported!
+  - For python binding, use the `proxy` keyword argument in the `SpeechService` constructor.
+- Fix: Now the `list-voices` command correctly handles the auth settings. (region, token, key)
+- Now you can specify the voice list API url when using the `list-voices` command.
+
 # v4.3.0-beta.2
 
 - Change the implementation of socks5 proxy.

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "aspeak"
-version = "4.3.0-beta.2"
+version = "4.3.0"
 edition = "2021"
 authors = ["kxxt <[email protected]>"]
 description = "A simple text-to-speech client for Azure TTS API."

README.md

@@ -48,7 +48,7 @@ From v4.1.0, You can install `aspeak-bin` from AUR.
 Installing from PyPI will also install the python binding of `aspeak` for you. Check [Library Usage#Python](#Python) for more information on using the python binding.
 
 ```bash
-pip install -U aspeak==4.3.0-beta.2
+pip install -U aspeak==4.3.0
 ```
 
 Now the prebuilt wheels are only available for x86_64 architecture.
@@ -108,6 +108,16 @@ $ aspeak --region <YOUR_REGION> --key <YOUR_SUBSCRIPTION_KEY>  text "Hello World
 
 If you are using a custom endpoint, you can use the `--endpoint` option instead of `--region`.
 
+From v4.3.0, you can let aspeak use a proxy server to connect to the endpoint. 
+For now, only http and socks5 proxies are supported (no https support yet). For example:
+
+```sh
+$ aspeak --proxy http://your_proxy_server:port text "Hello World"
+$ aspeak --proxy socks5://your_proxy_server:port text "Hello World"
+```
+
+aspeak also respects the `HTTP_PROXY`(or `http_proxy`) environment variable.
+
 To avoid repetition, you can store your authentication details
 in your aspeak profile.
 Read the following section for more details.

README.md.in

@@ -108,6 +108,16 @@ $ aspeak --region <YOUR_REGION> --key <YOUR_SUBSCRIPTION_KEY>  text "Hello World
 
 If you are using a custom endpoint, you can use the `--endpoint` option instead of `--region`.
 
+From v4.3.0, you can let aspeak use a proxy server to connect to the endpoint. 
+For now, only http and socks5 proxies are supported (no https support yet). For example:
+
+```sh
+$ aspeak --proxy http://your_proxy_server:port text "Hello World"
+$ aspeak --proxy socks5://your_proxy_server:port text "Hello World"
+```
+
+aspeak also respects the `HTTP_PROXY`(or `http_proxy`) environment variable.
+
 To avoid repetition, you can store your authentication details
 in your aspeak profile.
 Read the following section for more details.