Update nodegit to version 0.15.0 π #76
Closed
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.
Hello lovely humans,
nodegit just published its new version 0.15.0.
This version 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 nodegit.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isnβt right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while Iβm just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project β¨
You rock!
π΄
GitHub Release
This updates NodeGit to use the latest
HEAD
version of libgit2. The plan for staying on the official tagged releases of libgit2 is that they will get a maintenance branch and not-breaking API fixes will be backported to them. The first branch of this sort ismaint/0.14
. Going forward new releases of NodeGit will follow closely to themaster
branch of libgit2.Summary of changes that were brought in:
libgit2/libgit2@37dba1a
Changes or improvements
NodeGit.FetchOptions
, andNodeGit.PushOptions
now have aproxyOpts
field that accepts aNodeGit.ProxyOptions
object that allows NodeGit to use a proxy for all remote communicationNodeGit.MergeOptions
has adefaultDriver
field that lets the caller change the driver used to when both sides of a merge have changedAPI additions
Commit.createWithSignature
allows the caller to create a signed commit. There are no tests for this currently so it's labelled experimental.Blob
,Commit
,Tag
, andTree
all have a new prototypedup
method on them to make a low-level copy of the libgit2 object if needed.Odb#expandIds
is exposed which takes in a list of short ids and expands them in-place to the full id of the object in the databaseThe new version differs by 46 commits .
5d7517f
Update changelog to use better formatting.
957cf7c
Fix windows build
c64cbf9
Bump to version 0.15.0
e7bc03e
Merge pull request #1041 from nodegit/update-libgit2-head
09008d7
Bump to version 0.14.0
5f0fe1c
Merge pull request #1055 from nodegit/lifecycle-fixes
5119bb9
Fix
lifecycleScripts/postinstall
for electron/nwjs39e5fa9
Fix linter
0766ee6
Trim spawn stdout/stderr logs
3a83ddf
Fix build on npm@2/node@4
e7ff929
Fix build on linux
805edba
Fix build on windows
90ac3a5
Merge pull request #1058 from jorisroling/master
9d45b9a
changed references to entry.filename() to entry.name()
9543011
Handle legacy npm in lifecycle scripts
There are 46 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? β‘
greenkeeper upgrade