An in-range update of semantic-release is breaking the build 🚨

[greenkeeper[bot]]

Version 7.0.2 of semantic-release just got published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	7.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As semantic-release is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **bitHound - Code** null [Details](https://www.bithound.io/github/no23reason/react-geolocated/greenkeeper%2Fsemantic-release-7.0.2) - ❌ **bitHound - Dependencies** 2 failing dependencies. [Details](https://www.bithound.io/github/no23reason/react-geolocated/af2f0449ccaf1e3e0ffa9db7ca70370232adf995/dependencies/npm#filter-failing-dep) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/no23reason/react-geolocated/builds/265957304?utm_source=github_status&utm_medium=notification) - ✅ **codecov/project** 91.89% remains the same compared to 8ae8da6 [Details](https://codecov.io/gh/no23reason/react-geolocated/commit/af2f0449ccaf1e3e0ffa9db7ca70370232adf995) - ✅ **codecov/patch** Coverage not affected when comparing 8ae8da6...af2f044 [Details](https://codecov.io/gh/no23reason/react-geolocated/commit/af2f0449ccaf1e3e0ffa9db7ca70370232adf995)

---

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

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 7.0.1 your tests are passing again. Downgrade this dependency 📌.

[no23reason]

BitHound