This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
Update standard-version to the latest version 馃殌 #204
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 4.3.0 of standard-version was just published.
The version 4.3.0 is not covered by your current version range.
If you don鈥檛 accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of standard-version.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don鈥檛 have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 22 commits.
9a99607chore(release): 4.3.04fd3bc2feat: do not update/commit files in .gitignore (#230)c5e1ee2feat: publish only if commit+push succeed (#229)45fcad5feat(format-commit-message): support multiple %s in the messageb37bc66test(format-commit-message): add failing test cases3fdd7fafix: use theskipdefault value for skip cli arg (#211)709dae1fix: recommend--tagprerelease for npm publish of prereleases (#196)958daf4chore: add link to community slack (#202)2790e08chore(release): 4.2.0bc0fc53feat: add support forpackage-lock.json(#190)4b6d6dbchore(release): 4.1.0d31dcdbfeat: add support for skipping lifecycle steps, polish lifecycle work (#188)d073353feat: add dry-run mode (#187)dfd1d12feat: add prebump, postbump, precommit, lifecycle scripts (#186)86af7fcfeat: add support fornpm-shrinkwrap.json(#185)There are 22 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 馃尨