Gitfence

Gitfence 1.0.0-rc1

Released · Signed by Gitfence (Ed25519, key 728551a97150ace0) · 5 of 8 automated checks passed.

All releases · How the ledger works

What we shipped

FileSHA-256
Container image (amd64)sha256:b686a09bdb949c68016e9696fcd82c57fc2461041329727df9c656ed15e359c9
gitfence-linux-arm645fe4f74f5f98108580efde7f526f70df2bc66869d603dd7ee410b893107e5ec7
gitfence-linux-x64c29ff4df5a224a756add2d2034e160db044cf2734344e09abab6ba99f29eea11
SHA256SUMS9d3e3f46e2e70ba13ca6bf715bd919af2da50cd7dddb443fdf50e75559db15e7

Chain hash

The hash of this release's signed entry. The next release's entry includes it, and the published chain head on the releases page ends the chain.

3124bfa7d6d685c814873d9d39ef5e677b4e70b40645711759fdfcdbeebfe116

The full release record

Enterprise and self-hosted customers receive the complete record of this release (changes, test results, dependencies and the results of every automated check) in their admin settings and in the self-hosted release bundle. This entry commits to it: the SHA-256 of the record, as signed, is

3562a6e7f76cd112f5c5fd6c6b8cd3f651af45f643ec102778498275f844196a

so the record you receive is exactly the one the public chain names (how to check).

Verify

The check runs in your browser with WebCrypto: the signature on this entry and its link in the published chain. The only file it fetches is the index from this site.

Signed entry (JSON) · Detached signature · Published index · Command-line check