v0.14.14

RegistrationManagerImpl: catch IOException around refreshPreKeys

Previous attempt wrapped syncRemoteStorage but it's fire-and-forget
(no synchronous throw), so the compiler rejected the catch. The
actual source of the post-registration 403 is refreshPreKeys which
declares throws IOException.

Wrap that one and let registration finish even if pre-key upload
fails in the local dev stack.

Bump to 0.14.14.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

v0.14.12

TestConfig: 192.168.1.105 → 192.168.1.101; bump 0.14.12

Test environment URLs pegede på den forkerte IP (.105 i stedet for
.101 hvor Signal-Server faktisk kører).

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

v0.14.10

WhisperTrustStore: produce BKS keystore instead of JKS

BlacklistingTrustManager.createFor in signalservice-core loads the
trust store via BouncyCastle's BcKeyStoreSpi (hardcoded BKS format),
so the previous JKS-format in-memory store failed at runtime with
"Wrong version of key store" during /v2/send.

Register BouncyCastleProvider in a static initializer and build the
in-memory keystore as KeyStore.getInstance("BKS", "BC").

Bump version to 0.14.10.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

v0.14.8

build-image: pass SIGNAL_CLI_VERSION build-arg to Dockerfile

Dockerfile's COPY glob was hardcoded to *-SNAPSHOT.tar.gz, which
broke once we bumped to a real version (0.14.8). Read the version
from dist/VERSION in the workflow and pass it as a build-arg so the
COPY is exact.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

v0.14.7

Full Changelog: v0.14.6...v0.14.7

v0.14.6

Full Changelog: v0.0.2...v0.14.6

v0.0.2

Full Changelog: v0.0.1...v0.0.2

v0.0.1

Full Changelog: https://github.com/tvup/signal-cli/commits/v0.0.1