gim-hub 0.5.1

Status page.

• Status page: GET / and GET /status serve an HTML page with the version, build revision, platform, hub ID and public URL, so a browser opening the hub no longer gets a 404. Switched by GIM_HUB_STATUS_PAGE (stored live setting, default true; false answers 404 at both paths). See docs/operations.md.
• No database migration.
• Assets: gim-hub-linux-x86_64.tar.gz, gim-hub-linux-aarch64.tar.gz, each with an ed25519 .sig sidecar.

lode trusted key: f22e33416e94c5ba:jeWP-q9Mz89Vxm5Zq5Ss0kiPtBcthFKSlb0jfKCh1rs

gim-hub 0.5.0

Account deletion.

• Account deletion: DELETE /v2/users/{user_id} with a request signed by the user's root key (gim/root-request/v1: Gim-Key, Gim-Timestamp, Gim-Signature) removes the user's account, devices, handles, recovery backup, sessions, key packages, push registrations, hosting records and inbox. Group rosters are kept. Clients use it from "Delete account". See docs/api-v2.md and docs/identity.md ("Root-signed requests").
• No database migration.
• Assets: gim-hub-linux-x86_64.tar.gz, gim-hub-linux-aarch64.tar.gz, each with an ed25519 .sig sidecar.

lode trusted key: f22e33416e94c5ba:jeWP-q9Mz89Vxm5Zq5Ss0kiPtBcthFKSlb0jfKCh1rs

gim-hub 0.4.0

Configuration stored in SQLite, user allow/deny policy, admin token from the environment.

• Configuration in SQLite: every setting except the bootstrap ones (listen addresses, data dir, database path, admin listener and login) is stored in hub.db and managed in the admin UI Settings page, the admin API (/admin/api/settings) and the CLI gim-hub config list|get|set|unset. Precedence: environment variable > stored value > default; a setting set by the environment is read-only. Live settings apply at once, the others are marked "restart required". Secrets (push webhook secret, P2P PSK) are write-only, but stored in plaintext in hub.db: protect the database and its backups like a key file. An existing env-only deployment behaves as before.
• Federation allowlist: stored in the database and edited in the UI or with gim-hub config allowlist; GIM_HUB_FEDERATION_ALLOWLIST (file) still wins when set.
• User policy: GIM_HUB_USER_POLICY = open | allow | deny with a user list (admin UI "User policy" page, gim-hub config users). A not-admitted user cannot register or sign in (403 user_not_admitted) and loses their sessions; remote not-admitted users cannot claim key packages of, invite, or post in groups owned by this hub. See docs/api-v2.md, docs/s2s.md.
• Admin token: GIM_HUB_ADMIN_TOKEN (the value) as an alternative to GIM_HUB_ADMIN_TOKEN_FILE; setting both is a startup error. The file (or a Docker secret) remains the recommended way.
• Database migrations 0013 and 0014; a pre-migration backup is taken automatically.
• Assets: gim-hub-linux-x86_64.tar.gz, gim-hub-linux-aarch64.tar.gz, each with an ed25519 .sig sidecar.

lode trusted key: f22e33416e94c5ba:jeWP-q9Mz89Vxm5Zq5Ss0kiPtBcthFKSlb0jfKCh1rs

gim-hub 0.3.0

Admin UI, user suspension and a hub-to-hub reconnect fix.

• Admin UI and API (/admin/api/*), embedded in the binary and served only on a separate listener GIM_HUB_ADMIN_LISTEN (off by default). Login by admin token (GIM_HUB_ADMIN_TOKEN_FILE) or a trusted reverse-proxy identity header. Overview, users, federation allowlist, lode panel, read-only config, audit log. See docs/admin.md and deploy/lode/traefik-admin.yml.
• User suspension: a suspended user's sessions are deleted and POST /v2/auth/challenge / POST /v2/auth/session answer 403 user_suspended (docs/api-v2.md).
• Federation: a request on a stale connection to a restarted peer hub now closes it, redials and retries once (read-only and dedup-keyed operations only) instead of failing with peer_unavailable.
• Database migration 0012 (users.suspended_at, admin_audit, devices.created_at); a pre-migration backup is taken automatically.
• Assets: gim-hub-linux-x86_64.tar.gz, gim-hub-linux-aarch64.tar.gz, each with an ed25519 .sig sidecar.

lode trusted key: f22e33416e94c5ba:jeWP-q9Mz89Vxm5Zq5Ss0kiPtBcthFKSlb0jfKCh1rs

gim-hub 0.2.0

First release for the lode supervisor (bkhq/lode v0.1.0).

• Runs under lode: readiness handshake, release version in GET /v2/hub and gim-hub version, graceful SIGTERM stop.
• Online SQLite backup before pending migrations ($GIM_HUB_DATA_DIR/backups/, newest 3 kept); a binary that finds a newer schema exits without writing.
• Assets: gim-hub-linux-x86_64.tar.gz, gim-hub-linux-aarch64.tar.gz, each with an ed25519 .sig sidecar.
• Image: Dockerfile.lode; operator config: deploy/lode/lode.toml; see docs/operations.md "Running under lode".

lode trusted key: f22e33416e94c5ba:jeWP-q9Mz89Vxm5Zq5Ss0kiPtBcthFKSlb0jfKCh1rs