Compare commits

..

3 Commits

Author SHA1 Message Date
Stefan Meinecke
62ed3069d9
Merge 67105e14c19d9abf09a3ab133bd43da13662a7d6 into 056878fad7a74dc38a2ac74a056121e958d631a0 2026-04-23 10:23:53 +00:00
Stefan Meinecke
67105e14c1
Merge branch 'master' into fix/unauthenticated-socket-keepalive 2026-04-23 10:23:51 +00:00
AsamK
056878fad7 Bump version to 0.14.3 2026-04-22 23:16:58 +02:00
4 changed files with 18 additions and 3 deletions

View File

@ -1,10 +1,22 @@
# Changelog
## [Unreleased]
## [0.14.3] - 2026-04-22
### Fixed
- Fix sender key re-distribution on every group message (Thanks @meinecke)
### Improved
- Performance improvement when assigning admin role to multiple group members
- Increase disconnect timeout for websocket connections
- Release builds are now reproducible
### Changed
- Send message results now surface server-advised retry time for plain rate-limit (HTTP 413) failures, not only for proof-required challenges. The `retryAfterSeconds` field in JSON-RPC `SendMessageResult` is populated whenever the server sends a `Retry-After` header. The canonical way to distinguish proof-required failures remains `token != null`. Text output includes "retry after N seconds" when known.
- Add distinct JSON-RPC error code (6) for captcha rejection (Thanks @tonycpsu)
- No longer sends busy call response to allow linked devices to accept call
## [0.14.2] - 2026-04-04

View File

@ -10,7 +10,7 @@ plugins {
allprojects {
group = "org.asamk"
version = "0.14.3-SNAPSHOT"
version = "0.14.3"
}
java {

View File

@ -45,6 +45,9 @@
<content_attribute id="social-chat">intense</content_attribute>
</content_rating>
<releases>
<release version="0.14.3" date="2026-04-22">
<url type="details">https://github.com/AsamK/signal-cli/releases/tag/v0.14.3</url>
</release>
<release version="0.14.2" date="2026-04-04">
<url type="details">https://github.com/AsamK/signal-cli/releases/tag/v0.14.2</url>
</release>

View File

@ -1 +1 @@
0.90.0
0.92.1