RELEASE.md

Building a release candidate

To create a release candidate you must compress a local build.

Unsigned build

Zip files can be shared

# compress build folder to {manifest.name}.zip
# if CARDANO_NETWORK is not provided, it defaults to "testnet"
$ CARDANO_NETWORK=mainnet npm run prod:unsigned

(Chrome) Signed build

Crx are compressed and signed chrome extension bundles

# compress build folder to {manifest.name}.zip and crx
$ npm run prod:byron

Note: Chrome extensions update automatically

(Firefox) Signed build (XPI)

The same steps as Chrome also produce an xpi file. You can upload this directly to the EMURGO AMO account

Deploying new version

Update the version number in manifest files and in package.json

1. Create a new release on Github
2. Upload to Chrome store