You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The version 4.0.3 is not covered by your current version range.
If you don’t 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 @semantic-release/git.
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’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
set name/email of commit author and committer via Git env var (a58c357)
BREAKING CHANGES
the GIT_USERNAME and GIT_EMAIL environment variables are replaced by the Git environment variablesGIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL.
commit files from assets even if in they are in .gitignore (629dfc4)
BREAKING CHANGES
the .gitignore file is now ignored when adding files to the release commit
Each files matching a glob in assets will now be included in the release commit. The assets option has now to be configured to match exactly the the files that have to be commited, independently of the .gitignore file.
Commits
The new version differs by 3 commits.
629dfc4feat: commit files from assets even if in they are in .gitignore
fede564chore(package): update sinon to version 6.0.0
3969424chore(package): update nyc to version 12.0.1
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.0.3 of @semantic-release/git was just published.
The version 4.0.3 is not covered by your current version range.
If you don’t 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 @semantic-release/git.
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’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.0.34.0.3 (2018-05-01)
Bug Fixes
Commits
The new version differs by 3 commits.
5ed087b
fix(package): update fs-extra to version 6.0.0
8e70f1f
docs: update
assets
default valueb0169f6
chore(package): update sinon to version 5.0.0
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴