Update semantic-release to the latest version 🚀

[greenkeeper]

Version 7.0.1 of semantic-release just got published.

Dependency	semantic-release
Current Version	6.3.6
Type	devDependency

The version 7.0.1 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of semantic-release.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Release Notes

v7.0.1

7.0.1 (2017-08-14)

Bug Fixes

• post: Create a tag before makeing a release (3f85597)
• post: fix target_commitish to be the default branch (f148a61)

Commits

The new version differs by 9 commits.

• 3f85597 fix(post): Create a tag before makeing a release
• f148a61 fix(post): fix target_commitish to be the default branch
• 5b3bdd2 chore: remove console.log
• 64d84a0 chore(travis): drop builds in Node <4
• 1fa6d50 fix(package): update @semantic-release/release-notes-generator to version 3.0.1
• 6145bc9 docs(readme): add sgc (#386)
• 609b46f docs(README): minor typo (#376)
• 76cd99c chore(package): update standard to version 9.0.0
• 22dc640 chore(package): update tap to version 10.0.1

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 7.0.2 just got published.

Update to this version instead 🚀

Release Notes

v7.0.2

7.0.2 (2017-08-16)

Bug Fixes

• post: create v1.2.3 tag tag instead of branch (3f85597)

  Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY error :( To recover, follow these steps:

  1. Make sure you are on your main branch and pulled the latest changes from remote
  2. Edit the package.json file, set "version" to what ever should have been released. As an example, let's say the new version number would be 1.2.3. Save the change
  3. run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
  4. revert the changes
  5. create a tag with git tag v1.2.3 (put in the same version as in step 2. Push the tag to GitHub with git push --tags
  6. Manually create a release for the tag

  This will fix the problem and everything will work automagically again from here on now.

Commits

The new version differs by 1 commits.

• 0c79a9b fix(post): create git tag properly

See the full diff