Print new version

If incrementing version, print it. For example here I do not see which version is new

> semantic-action pre && npm run deploy && semantic-action post
(node:4201) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
semantic-action WARN invalid config loglevel="notice"
[Travis Deploy Once]: Success at attempt 1. All 1 jobs passed.
found 2 semantic commit(s)
[ { firstLine: 'fix(dev): another missing dev package added',
    type: 'fix',
    scope: 'dev',
    subject: 'another missing dev package added' },
  { firstLine: 'fix(dev): add missing dependency',
    type: 'fix',
    scope: 'dev',
    subject: 'add missing dependency' } ]
PASS: Current version does not break dependents
dont-crack finishing with success? true
> test-semantic-deploy-with-now@0.0.0 deploy /home/travis/build/bahmutov/test-semantic-deploy-with-now
> now-pipeline --alias test-semantic-deploy-with-now-123 --test 'npm run unit'
BOOTED test-semantic-deploy-with-now-cvuriwatjo.now.sh limit 600 seconds
BUILDING test-semantic-deploy-with-now-cvuriwatjo.now.sh limit 595 seconds
READY test-semantic-deploy-with-now-cvuriwatjo.now.sh limit 590 seconds
deployed to url https://test-semantic-deploy-with-now-cvuriwatjo.now.sh
testing url https://test-semantic-deploy-with-now-cvuriwatjo.now.sh
passing it as env variable NOW_URL
test command "npm run unit"
running "npm" with extra env keys [ 'NOW_URL' ]

The reported entry point is the semantic-action pre && npm run deploy && semantic-action post command; start by locating where version increments are reported in that command's output. Confirm the output includes the new version when an increment occurs, using the example log as the expected scenario. No file or test is named in the issue.