Bump version

diff --git a/CHANGELOG.md b/CHANGELOG.md
index fa27507d0dd87960a164e43f1d4ae78ecc6cf3d9..26b96784eb365b7e26c86424ddb6e0570657513a 100644 (file)
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,16 +1,31 @@
 # Changelog
 
 ## [Unreleased]
 # Changelog
 
 ## [Unreleased]

+
+## [0.9.0] - 2021-09-12
+**Attention**: Now requires native libsignal-client version 0.9
+

 ### Breaking changes
 ### Breaking changes

-- Removed deprecated `--json` parameter, use `--output=json` instead
+- Removed deprecated `--json` parameter, use global parameter `--output=json` instead

 - Json output format of `listGroups` command changed:
 - Json output format of `listGroups` command changed:

-  Members are now arrays of `{"number":"...","uuid":"..."}` instead of arrays of strings.
+  Members are now arrays of `{"number":"...","uuid":"..."}` objects instead of arrays of strings.

 - Removed deprecated fallback data paths, only `$XDG_DATA_HOME/signal-cli` is used now
   For those still using the old paths (`$HOME/.config/signal`, `$HOME/.config/textsecure`) you need to move those to the new location.
 
 ### Added
 - New global parameter `--trust-new-identities=always` to allow trusting any new identity key without verification
 - Removed deprecated fallback data paths, only `$XDG_DATA_HOME/signal-cli` is used now
   For those still using the old paths (`$HOME/.config/signal`, `$HOME/.config/textsecure`) you need to move those to the new location.
 
 ### Added
 - New global parameter `--trust-new-identities=always` to allow trusting any new identity key without verification

-- New parameter `--device-name` for `updateAccount` command to update the device name
+- New parameter `--device-name` for `updateAccount` command to change the device name (also works for the main device)
+- New SignalControl DBus interface, to register/verify/link new accounts
+- New `jsonRpc` command that provides a JSON-RPC based API on stdout/stdin
+- Support for announcement groups
+- New parameter `--set-permission-send-messages` for `updateGroup` to create an announcement group
+- New `sendReceipt` command to send read and viewed receipts
+- Support for receiving sender key messages, mobile apps can now send messages more efficiently with server-side fan-out to groups with signal-cli members.
+- Support for reading data from remote Signal storage. Now v2 groups will be shown after linking a new device.
+- New `submitRateLimitChallenge` command that can be used to lift some rate-limits by solving a captcha
+
+### Fixed
+- Store identity key correctly when sending a message after a recipient has changed keys

 
 ## [0.8.5] - 2021-08-07
 ### Added
 
 ## [0.8.5] - 2021-08-07
 ### Added

diff --git a/README.md b/README.md
index 9658dcba11ac244ccee5b8390dc8dbe7e74ab2ac..178573fe32ced0fe3f6841036825352242912fc6 100644 (file)
--- a/README.md
+++ b/README.md
@@ -4,6 +4,7 @@ signal-cli is a commandline interface for [libsignal-service-java](https://githu
 To be able to link to an existing Signal-Android/signal-cli instance, signal-cli uses a [patched libsignal-service-java](https://github.com/AsamK/libsignal-service-java), because libsignal-service-java does not yet support [provisioning as a linked device](https://github.com/WhisperSystems/libsignal-service-java/pull/21).
 For registering you need a phone number where you can receive SMS or incoming calls.
 signal-cli is primarily intended to be used on servers to notify admins of important events. For this use-case, it has a dbus interface ([man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-dbus.5.adoc)), that can be used to send messages from any programming language that has dbus bindings.
 To be able to link to an existing Signal-Android/signal-cli instance, signal-cli uses a [patched libsignal-service-java](https://github.com/AsamK/libsignal-service-java), because libsignal-service-java does not yet support [provisioning as a linked device](https://github.com/WhisperSystems/libsignal-service-java/pull/21).
 For registering you need a phone number where you can receive SMS or incoming calls.
 signal-cli is primarily intended to be used on servers to notify admins of important events. For this use-case, it has a dbus interface ([man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-dbus.5.adoc)), that can be used to send messages from any programming language that has dbus bindings.

+It also has a JSON-RPC based interface, see the [documentation](https://github.com/AsamK/signal-cli/wiki/JSON-RPC-service) for more information.

 
 ## Installation
 
 
 ## Installation
 

diff --git a/build.gradle.kts b/build.gradle.kts
index c7de229c6f984452aa1c9669b00703dc1a3742cc..37b94492b1ce3e9cf54a0df587c42f92f35a7c08 100644 (file)
--- a/build.gradle.kts
+++ b/build.gradle.kts
@@ -5,7 +5,7 @@ plugins {
     `check-lib-versions`
 }
 
     `check-lib-versions`
 }
 

-version = "0.8.5"
+version = "0.9.0"

 
 java {
     sourceCompatibility = JavaVersion.VERSION_11
 
 java {
     sourceCompatibility = JavaVersion.VERSION_11

diff --git a/man/signal-cli.1.adoc b/man/signal-cli.1.adoc
index b52612beb3d0980db8de5a97e00e74194406648d..573ade7c432e01d4f7b98aa94284209c78dff09e 100644 (file)
--- a/man/signal-cli.1.adoc
+++ b/man/signal-cli.1.adoc
@@ -362,6 +362,8 @@ Trust all known keys of this user, only use this for testing.
 
 *-v* VERIFIED_SAFETY_NUMBER, *--verified-safety-number* VERIFIED_SAFETY_NUMBER::
 Specify the safety number of the key, only use this option if you have verified the safety number.
 
 *-v* VERIFIED_SAFETY_NUMBER, *--verified-safety-number* VERIFIED_SAFETY_NUMBER::
 Specify the safety number of the key, only use this option if you have verified the safety number.

+Can be either the plain text numbers shown in the app or the bytes from the QR-code,
+encoded as base64.

 
 === updateProfile
 
 
 === updateProfile