This repository has been archived by the owner on Mar 23, 2021. It is now read-only.
Releases: comit-network/create-comit-app
Releases · comit-network/create-comit-app
comit-scripts-0.8.0
First comit-scripts standalone release:
- The booting of a development environment,
start-env
, is now isolated to thecomit-scripts
package.
Which means that COMIT App should import dev dependencycomit-scripts
instead ofcreate-comit-app
.
See../create/CHANGELOG.md
for historical changes.
0.7.0
Fix import
0.6.0
Added
- Windows support 🎉.
Release 0.5.2
Changed
- Upgrade all examples and new project to
comit-sdk@0.7.1
.
Release 0.5.1
- Upgrade separate_apps example to comit-sdk 0.7.01 to fix maker auto-accept.
- Add code comments in separate_apps to describe the behaviour and help app developers understand how to use COMIT SDK.
Release 0.5.0
Changed
separate_apps
example now uses the negotiation protocol provided by comit-sdk.- Upgrade to
comit-rs:0.4.0
- Upgrade all examples and new project to
comit-sdk@0.7.0
.
0.4.0
Release 0.4.0
ERC20 Support!
Added
- Deploy an ERC20 contract on the Ethereum node and give tokens to both parties. The address of the token contract is written to the env file as
ERC20_CONTRACT_ADDRESS
.
Changed
- Migrate parts of the code base to async/await 🎉
0.2.1
0.2.0
Added
- Ensure that all temporary folders are cleaned up when shutting down start-env.
- Display clear message if start-env is started twice on the same machine.
Changed
- Move start-env env file to
~/.create-comit-app/env
so that the user does not have to start it from inside the project folder. - If a signal (e.g. CTRL-C) is sent while
start-env
is booting, it waits for the action in progress (e.g., starting docker container) and then stops and properly cleans up the environment. - Improve code quality to avoid artifacts remaining after a failure happens while booting start-env.
- Migrate to comit-rs 0.3.0. Only the
cnd
docker is now needed! - Move the env file from
./.env
to~/.create-comit-app/env
to improve usability. - Only pull docker images if they are not present locally, this allows offline usage of the
start-env
command.