[] I've ensured the unit and smoke tests are still passing - either by running yarn test:unit and yarn test:smoke:[ios|android] or by checking the appropriate CircleCI builds' statuses.
[x] I've manually tested whether the changes I made work as expected.
Motivation and Context
I went to deploy a release from a relatively fresh machine and ended up in this state:
⠙ yarn release:update:turtle-cli-example
$ ./scripts/updateTurtleCliExampleRepo.sh
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
✖ yarn release:update:turtle-cli-example
ERROR ./scripts/updateTurtleCliExampleRepo.sh: line 17: jq: command not found
error Command failed with exit code 127.
Rolling back changes...
error Command failed with exit code 1.
It was pretty unclear how I could recover from this, and so it's best to avoid getting into this state if possible.
Description
I added some verification that the jq executable is available and bail out if not.
Checklist
yarn test:unitandyarn test:smoke:[ios|android]or by checking the appropriate CircleCI builds' statuses.Motivation and Context
I went to deploy a release from a relatively fresh machine and ended up in this state:
It was pretty unclear how I could recover from this, and so it's best to avoid getting into this state if possible.
Description
I added some verification that the
jqexecutable is available and bail out if not.