Development
#
BuildWe are suggesting to use lets-dev
name for development binary, so you could
have stable lets
version untouched.
To build a binary:
To install in system
Or if you already have lets
installed in your system:
path
- your custom executable $PATH, defaults to /usr/local/bin
After install - check version of lets - lets-dev --version
- it should be development
It will install lets-dev
to /usr/local/bin/lets-dev, or wherever you`ve specified in path, and set version to development with current tag and timestamp
#
TestTo run all tests:
To run unit tests:
To get coverage:
To test lets
output we are using bats
- bash automated testing:
#
ReleaseTo release a new version:
This will create an annotated tag with 0.0.1 and run git push --tags
#
Versioninglets
releases must be backward compatible. That means every new lets
release must work with old configs.
For situations like e.g. new functionality, there is a version
in lets.yaml
which specifies minimum required lets
version.
If lets
version installed on the user machine is less than the one specified in config it will show and error and ask the user to upgrade lets
version.