v0.20.0

0.20.0 (2020-06-16)

BREAKING CHANGE

From this version, mergeStrategy no longer exists.

If you don't know what it is,

Make sure you run shipjs trigger only on the branches you've specified.

If you have a CircleCI config like the following:

version: 2
jobs:
  shipjs_trigger:
    docker:
      - image: "circleci/node:latest"
    steps:
      - checkout
      - run:
          name: Install
          command: yarn install
      - run:
          name: Triggering Ship.js to Release
          command: yarn shipjs trigger
workflows:
  version: 2
  release_if_needed:
    jobs:
      - shipjs_trigger

then, modify the last part like the following:

workflows:
  version: 2
  release_if_needed:
    jobs:
      - shipjs_trigger:
          filters:
            branches:
              only:
                - master # or whatever branch you'd like (normally your base branch)

This ensures shipjs trigger runs only on the specified branches.

If you were using mergeStrategy,

Ship.js used to have toSameBranch and toReleaseBranch strategies. Now they're gone and it only works like toSameBranch strategy. As explained above, you need to specify branches where to run shipjs trigger, though.

If you were using toReleaseBranch, there is a workaround. You can read Release Snapshot to achieve what you used to do.

Bug Fixes

• prepare: return correct releaseType (#885) (7d918f6)
• setup: get correct remote branches (#883) (551dde0)
• setup: update circleci node version to v12 (#884) (6579294)
• setup: use current branch when there is no remote at setup flow (#881) (5a0e152)