SIM Hub Dev v0.17.4-dev.8

SIM Hub Dev 0.17.4-dev.8

Experimental development prerelease. Test on isolated devices and data volumes; do not deploy over Stable.

SIM Hub Dev v0.17.4-dev.7

SIM Hub Dev 0.17.4-dev.7

Experimental development prerelease. Test on isolated devices and data volumes; do not deploy over Stable.

SIM Hub Dev v0.17.4-dev.6

SIM Hub Dev 0.17.4-dev.6

Experimental development prerelease. Test on isolated devices and data volumes; do not deploy over Stable.

SIM Hub v0.17.4

SIM Hub v0.17.4

Downloadable verified Stable server packages

Changes

• Add a version-matched Rootless Docker deployment ZIP to GitHub Stable Releases alongside the signed Android APK and OCI image.
• Pin server installation to an immutable GHCR digest and channel-specific Sigstore/Cosign GitHub Actions identity; refuse cross-channel deployments.
• Preserve Stable E2EE, SMS and update behavior, with no experimental P2P/WebRTC dependency or database schema migration.
• Extend update manifests additively with deployment package identity and SHA-256; include deterministic archive regression tests.

Verification and compatibility

The signed APK and Relay OCI image are built and verified by the release workflow. Hardware-specific OEM background behavior, permissions, biometric prompts and foldable layouts still require physical-device acceptance testing.

For detailed changes and upgrade instructions, see CHANGELOG.md and README.md.

SIM Hub Dev v0.17.4-dev.5

SIM Hub Dev 0.17.4-dev.5

Experimental development prerelease. Test on isolated devices and data volumes; do not deploy over Stable.

SIM Hub v0.17.3

SIM Hub v0.17.3

Stable/Dev release separation and verified updater rollout

Changes

• Introduce independent Stable and Dev release channels with explicit version identity in the Web management UI, signed manifests and Android.
• Preserve the existing Stable package and GitHub releases/latest upgrade path; the separately installable Dev app is com.blackkcold.simhub.dev.
• Add channel-pinned rootless Docker upgrades with a distinct Dev systemd unit, separate Compose project/port and channel-specific Cosign workflow verification.
• Establish signed Dev GitHub Pre-release and GHCR packaging alongside the unchanged Stable release pipeline.
• Fail closed when experimental P2P/WebRTC modules appear in Stable release inputs or APK native artifacts.
• This Stable version does not include P2P or WebRTC; experimental P2P development belongs exclusively to the Dev channel.
• No database schema upgrade or E2EE protocol change is required for this release.

Verification and compatibility

The signed APK and Relay OCI image are built and verified by the release workflow. Hardware-specific OEM background behavior, permissions, biometric prompts and foldable layouts still require physical-device acceptance testing.

For detailed changes and upgrade instructions, see CHANGELOG.md and README.md.

SIM Hub Dev v0.17.3-dev.3

SIM Hub Dev 0.17.3-dev.3

Experimental development prerelease. Test on isolated devices and data volumes; do not deploy over Stable.

SIM Hub Dev v0.17.2-dev.1

SIM Hub Dev 0.17.2-dev.1

Experimental development prerelease. Test on isolated devices and data volumes; do not deploy over Stable.

SIM Hub v0.17.2

SIM Hub v0.17.2

Main reliability, native reply safety and UX hardening

Changes

• Separate native management SMS contact display labels from the actual recipient address; reply actions use the verified address and never compose SMS to a display name.
• Bound native conversation scrolling within the available workspace, expose loading feedback without duplicated indicators, and localize high-traffic controller and pairing screens.
• Invalidate native SMS-history cursors and pending refresh state when the locally protected Controller workspace locks.
• Advance Web encrypted SMS-history pagination only after the current Vault and data-generation ingest succeeds.
• Isolate SIM Hub Service Worker shell cache deletions; offline JavaScript/CSS misses return network errors rather than HTML with an incorrect MIME type.
• Expand Playwright viewport coverage and add Service Worker / SMS reply regression tests. Add Python and container dependency update coverage.
• Replace the hardcoded release trigger path with version-aware validation that requires the matching trigger to change in the publishing push.
• Correct documentation of Relay SMS event retention: the current default of zero preserves encrypted history until explicitly purged or retention is configured.
• This release does not merge P2P PR #84, change the E2EE protocol or grant hardware-auth-bound Keystore guarantees. Closed-browser Web Push, physical-SIM/OEM acceptance and app-store policy review remain separate external gates.

Verification and compatibility

The signed APK and Relay OCI image are built and verified by the release workflow. Hardware-specific OEM background behavior, permissions, biometric prompts and foldable layouts still require physical-device acceptance testing.

For detailed changes and upgrade instructions, see CHANGELOG.md and README.md.

SIM Hub v0.17.1

SIM Hub v0.17.1

Notification diagnostics and consistent settings layout

Changes

• Correct native Android SIM-node settings destination spacing in both compact and foldable/tablet layouts without changing pairing, SMS modes or encrypted data.
• Apply a consistent Web settings form rhythm, fixing nested shared-Vault password inputs and action spacing across responsive layouts.
• Align browser notification permission labels with actual grant/deny/paused states, refresh state on focus and permission changes, and make test actions report worker and delivery-request failures.
• Add optional system notifications while the management page is visible; bound Service Worker readiness waits to five seconds and report failed registration rather than silently suppressing errors.
• Preserve metadata-only browser notification privacy, retire expired history entries, and restore notification deep links after administrator login and Vault unlock.
• Expand automated Web regression coverage for permission controls, foreground preferences, history retention, Vault geometry and cold notification deep links.
• Browser notifications still require the Web/PWA to be running; closed-browser Web Push and guaranteed operating-system banners are not implied. Physical-device notification and foldable acceptance remain separate from CI.

Verification and compatibility

The signed APK and Relay OCI image are built and verified by the release workflow. Hardware-specific OEM background behavior, permissions, biometric prompts and foldable layouts still require physical-device acceptance testing.

For detailed changes and upgrade instructions, see CHANGELOG.md and README.md.