Closed greenkeeper[bot] closed 7 years ago
Merging #184 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #184 +/- ##
=======================================
Coverage 92.94% 92.94%
=======================================
Files 9 9
Lines 241 241
=======================================
Hits 224 224
Misses 17 17
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update b71f525...f64dff3. Read the comment docs.
Version 0.3.0 of s3-recursive-uploader just got published.
The version 0.3.0 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 s3-recursive-uploader. 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.
Commits
The new version differs by 11 commits.
52db226
v0.3.0
c7dcb63
update lockfile
b120005
fix comment
f8c78b6
Merge branch 'master' of github.com:dawson-org/s3-recursive-uploader
2d8a478
chore(package): update ava to version 0.19.0
fe66607
chore(package): update aws-sdk to version 2.60.0
6b9209b
Allow specifying public-read ACL for files (#5)
b0d0b98
pass ACL directly to s3.upload
a145d1a
Allow specifying public-read ACL for files
c514cc2
Add .idea/ to .gitignore
a60f7c7
Add Greenkeeper badge 🌴 (#1)
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: