Fulla v1.2.0
[1.2.0] - 2026-09-14
Added
- website: Docusaurus blog module + launch-post draft frame
- blog: Launch-post charts — five-scenario + cold-start, reproducible
Fixed
- security: 2026-09 audit — P0 batch (nonce, revocation, issuance guards)
- ci: PR #197 review — migration/api baselines, nonce length cap, branch coverage
- ci: Strict-JSON configs — drop jsoncpp-only // comments
- deploy: Rehearsal findings — migrate build section, doc drift, bootstrap password passthrough
- deploy: PR #199 review — --build on migrate run, AUTO_MIGRATE drift sweep, zh-CN guide sync
- auth: Send verification email on registration + unauthenticated resend (issue #198)
- auth: Guard email-verification against memory-storage mode
Documentation
- support: Route SDK users (Python/Go clients + C++ embed) to the right entry points
- blog: Launch post — full draft prose (all five sections)
Testing
- auth: Leave-no-trace cleanup in email-verification tests
Other
- ci: Normalize test names to Unit_OAuth2_ prefix (naming gate)
- ci: Test names follow Unit__ convention (naming gate)
Verification
Images are signed with cosign (keyless, GitHub OIDC):
cosign verify ghcr.io/voidvec/fulla-backend:1.2.0 \
--certificate-identity-regexp 'https://github.com/voidvec/fulla/.github/workflows/release.yml.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comSPDX SBOMs for the three images and the source tree are attached,
as is the SDK tarball checksum:
sha256sum -c fulla-sdk-1.2.0-linux-x86_64.tar.gz.sha256