The version 4.3.5 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 Notesv4.3.5
4.3.5 (2015-09-16)
Bug Fixes
commits: handle failing git command correctly and show meaningful error (772494e7, closes #83)
Commits
The new version differs by 18 commits (ahead by 18, behind by 109).
676d2d6Merge pull request #86 from semantic-release/badger-fix-git-contains
772494efix(commits): handle failing git command correctly and show meaningful error
f3c1314test(mocks): correctly fail git command when ref not in history
017142edocs(README): smaller fixes and clarifications
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).
varjmes
commented
7 years ago
Version 4.3.5 of semantic-release just got published.
The version 4.3.5 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
v4.3.54.3.5 (2015-09-16)
Bug Fixes
Commits
The new version differs by 18 commits (ahead by 18, behind by 109).
676d2d6Merge pull request #86 from semantic-release/badger-fix-git-contains772494efix(commits): handle failing git command correctly and show meaningful errorf3c1314test(mocks): correctly fail git command when ref not in history017142edocs(README): smaller fixes and clarifications3251a51docs(README): add egghead.io tutorial5dc85d2chore: make repo "commitizen friendly"527c45ffix: write version to shrinkwrap if existent3554d1adocs(README): fix badge links6f28f31chore: setup release branchd0fc38cchore(travis): enable travis_after_all5711e95fix: revert undeclared breaking changee55b70ddocs(README): list plugins and more talks399da06fix(condition-travis): remove need for python script travis_after_allee2a730chore(travis): upload coverage from all jobs03534e5fix(registry): be better at using the correct registry (relevant for npme)There are 18 commits in total. 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: