# AccessHub 0.2.0-alpha.2

Release commit: fa92bc5dac49e0a7f4dcc3b71b9e3baf5cb04ad4
Release workflow: https://github.com/SaiedAwad/accesshub/actions/runs/38945287826
Both acceptance/publication and clean anonymous-installation jobs passed.
Portable Docker checks 38945287894 also passed.

Verified: exactly five services; HTTPS setup/login and secure cookies;
restricted SQL and UID credential boundaries; administrator HBA rejection;
LDAP TLS; enrollment-token expiry/concurrency/replay; all-volume backup/restore;
required-worker failure shutdown/restart; and private-leaf certificate renewal.

The existing-data test creates an alpha.1 administrator, Linux user, groups,
host, memberships and access policy. Upgrade, rollback and repeat upgrade all
preserve data/password hashes and the website CA. A valid legacy administrator
password cannot connect over the database network after upgrading.

The database reuses the thin patched PostgreSQL 18.6 base by immutable digest;
AccessHub initialization and renewal now run in API. No new security exception
was added. The exact database scan has no High/Critical findings. Existing
time-bounded API/directory Debian reviews remain through November 14, 2026.

Only API receives a new image tag. Database/proxy/gateway/directory dependencies
are reused without overwriting old tags. Preserve all named volumes during
upgrade, and retain the previous Compose/.env and full stopped-stack backup.