Release

CodeChain would be published irregularly using semver syntax. You can see all the release and change logs in here.

The public API of CodeChain is JSON RPC and Network Protocol. So the major version would be increased when one of them is changed without backward compatibility.

How to release binary

Run release build

touch codechain/main.rs # It guarantees to update the commit hash.
cargo build --release

Calculate a checksum

Use sha256 for checksum

shasum -a 256 codechain

Compress the binary file

• Set version

CODECHAIN_VERSION="1.0.0"

• Compress the binary file

tar cvfz codechain-${CODECHAIN_VERSION}-$(uname -m)-$(echo $(uname) | tr '[:upper:]' '[:lower:]').tar.gz codechain

Upload the binary file with checksum

• template

| OS    | Binary                    | SHA256     |
|-------|---------------------------|------------|
| Linux | [{filename}]({file path}) | {checksum} |
| OS X  | [{filename}]({file path}) | {checksum} |