Releases & Verification
Verify official Conceal Core and Guardian releases before installation or upgrade.
This guide covers Core 6.7.5 and Guardian 0.7.8. Before installation, check the releases page and confirm the tag, asset, release notes, checksum, and signature information for the file you plan to run.
Documented release set
| Component | Documented version | Official release record |
|---|---|---|
| Core | 6.7.5 | Core releases |
| Desktop | 6.7.8 | Desktop releases |
| Web Wallet | v2.1.4 | Web Wallet releases |
| Android | v6.0.4-f-droid | Android releases |
| Guardian | v0.7.8 | Guardian releases |
| Conceal API | 0.8.8 | npm registry metadata |
| JS Library | v0.3.1 | conceal-lib-js releases |
| Wallet SDK | v0.2.14 | conceal-wallet-sdk releases |
The documentation checks these versions against GitHub Releases and the npm registry each week. The table is a reviewed documentation baseline, not a substitute for checking the release source immediately before installing.
Verification workflow
- Navigate directly to the applicable official releases page rather than following an attachment or a link sent in a message.
- Match the release tag and asset to the platform and architecture you intend to run.
- Obtain the checksum or signature from the same official release record, then verify the downloaded asset with the documented method for your platform.
- Stop if the asset, integrity material, signing identity, or release notes do not match what you expected. Resolve the discrepancy from the official repository before running it.
- Back up relevant local data before an upgrade and keep the previous working state available until the new version has been checked.
Guardian releases
Guardian is distributed separately from Core. Verify it as a separate component, including its own version, platform asset, release notes, and checksum. Do not assume that matching version numbers, installation locations, or update schedules imply compatibility.
Source builds
If you build from source, record the repository commit or tag, build environment, dependency versions, and resulting artifact hash. Review the current Core build documentation before treating a local build as equivalent to a published release.