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.
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).
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:
Make sure you are on your main branch and pulled the latest changes from remote
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
run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
revert the changes
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
Manually create a release for the tag
This will fix the problem and everything will work automagically again from here on now.
Version 7.0.1 of semantic-release just got published.
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.17.0.1 (2017-08-14)
Bug Fixes
Commits
The new version differs by 9 commits.
3f85597fix(post): Create a tag before makeing a releasef148a61fix(post): fix target_commitish to be the default branch5b3bdd2chore: remove console.log64d84a0chore(travis): drop builds in Node <41fa6d50fix(package): update @semantic-release/release-notes-generator to version 3.0.16145bc9docs(readme): add sgc (#386)609b46fdocs(README): minor typo (#376)76cd99cchore(package): update standard to version 9.0.022dc640chore(package): update tap to version 10.0.1See 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).Version 7.0.2 just got published.
Update to this version instead 🚀
Release Notes
v7.0.27.0.2 (2017-08-16)
Bug Fixes
post: create
v1.2.3tag tag instead of branch (3f85597)Note that if a version was released with v7.0.1, you will run into the
ENOTINHISTORYerror :( To recover, follow these steps:"version"to what ever should have been released. As an example, let's say the new version number would be1.2.3. Save the changenpm publishto release the new version. Make sure to run any pre-publish tasks first if you have anygit tag v1.2.3(put in the same version as in step 2. Push the tag to GitHub withgit push --tagsThis will fix the problem and everything will work automagically again from here on now.
Commits
The new version differs by 1 commits.
0c79a9bfix(post): create git tag properlySee the full diff
Your Greenkeeper Bot :palm_tree: