Update tar to the latest version 🚀 #1677
Merged
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.1.0 of tar was just published.
The version 4.1.0 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 tar.
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.
Commits
The new version differs by 12 commits.
61908e6
v4.1.0
20d9f56
use tap v11
5ae09b9
Add noMtime flag for tar creation
1f331ef
[email protected]
c633075
force colors in CI
850a6ec
Linux does not allow setting file pos with a+ open flag
f82e1f5
test: no need to dump huge strings in TAP output
b1e6c1d
bump mutate-fs to stop callstack failures
984b179
remove corrupt file not used for any porpoise
4428a4d
unpack: don't use stream obj for sync files
69b98b4
Use fs-minipass's autoClose:false support
6c703c9
use fs-minipass streams where appropriate
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 🌴