-
Notifications
You must be signed in to change notification settings - Fork 267
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: isaacs/node-tar
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v6.2.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: isaacs/node-tar
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.0.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 14 commits
- 205 files changed
- 1 contributor
Commits on Mar 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 0510c9e - Browse repository at this point
Copy the full SHA 0510c9eView commit details
Commits on Apr 8, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 114c7ac - Browse repository at this point
Copy the full SHA 114c7acView commit details
Commits on Apr 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9522a69 - Browse repository at this point
Copy the full SHA 9522a69View commit details -
changelog v7, flip default chmod behavior
The `noChmod` option is deprecated, and replaced with the `chmod` option. The default is now to *not* explicitly set the mode of created filesystem entries. This is a deviation from `tar(1)` implementations, but prevents the need to call `process.umask()`, which is deprecated and not thread safe. To still set modes explicitly, while avoiding the need to call `process.umask()`, a `processUmask` numeric option may now be provided along with `chmod: true`.
Configuration menu - View commit details
-
Copy full SHA for 734434c - Browse repository at this point
Copy the full SHA 734434cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 578f34f - Browse repository at this point
Copy the full SHA 578f34fView commit details -
Configuration menu - View commit details
-
Copy full SHA for dfb6b6c - Browse repository at this point
Copy the full SHA dfb6b6cView commit details -
Configuration menu - View commit details
-
Copy full SHA for ae9ce7e - Browse repository at this point
Copy the full SHA ae9ce7eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2330416 - Browse repository at this point
Copy the full SHA 2330416View commit details -
unpack test: use modern tap features
This replaces a lot of manual mkdir/rimraf with t.testdir()
Configuration menu - View commit details
-
Copy full SHA for b3afdbb - Browse repository at this point
Copy the full SHA b3afdbbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 314ec7e - Browse repository at this point
Copy the full SHA 314ec7eView commit details -
Properly handle long linkpath in PaxHeader
tar-stream creates some interesting tarballs, but they are technically allowed, and should be handled properly. Fix: #312 Also, this cleans up a flaky race condition in the unpack test.
Configuration menu - View commit details
-
Copy full SHA for 2d89a4e - Browse repository at this point
Copy the full SHA 2d89a4eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9a260c2 - Browse repository at this point
Copy the full SHA 9a260c2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 957da75 - Browse repository at this point
Copy the full SHA 957da75View commit details -
Configuration menu - View commit details
-
Copy full SHA for b0fbdea - Browse repository at this point
Copy the full SHA b0fbdeaView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v6.2.1...v7.0.0