Release notes
OpsProbe v0.3.57: persistent shared reports.
A focused release that makes report sharing durable and points social posts back to the OpsProbe evidence page instead of the checked website.
Quick answer
X, LinkedIn, copy-link, and native share actions now use the canonical OpsProbe report URL. Shared reports are persisted as redacted local JSON snapshots, and the PNG preview path renders from the completed probe payload.
What changed
- Normalized every public sharing action to
https://opsprobe.com/report.html?id=<report-id>. - Persisted redacted shared reports under the configured local share directory instead of relying on Redis after creation.
- Kept Redis limited to the 10-minute, single-use draft token used to create a report.
- Added report-page Open Graph and Twitter Card metadata for OpsProbe report crawlers.
- Fixed share-image generation so the PNG editor and download path receive the completed probe payload.
- Added the production
OPSPROBE_SHARE_DIRsystemd setting and a compatibility/reportNginx route.
Privacy boundary
Persisted shared reports remain privacy-limited snapshots. Raw response bodies, request and response headers, certificate serial numbers, remote addresses, and user identity are excluded from the saved payload.
Migration and rollback
No database migration is required. Production must keep OPSPROBE_SHARE_DIR writable by the API service. Rollback restores the previous API binary and static bundle while leaving the share-report directory in place for forward compatibility.