Closed aphelionz closed 6 years ago
@RichardLitt Check one more time.
4.2.0
~npm build
npm build:examples
npm audit fix
@aphelionz thank you, looking good 👍
However, we shouldn't update the package version here as we would do that only upon on a npm new release, from master. That is, the package version gets updated manually as part of the npm release process and shouldn't be changed in PRs.
@haadcode roger that. I'll change it back
@haadcode all set!
LGTM 👍
@haadcode Would Greenkeeper help here?
@RichardLitt we had Greenkeeper for all the ecosystem modules in the past. We turned it off because, well, it wasn't so helpful (more noise than signal). This was couple of years ago, they have prolly improved on it and generally if people feel like it can be helpful, we can definitely start using it again 👍
Ah, yeah, I remember that. I think it's a bit better now - but keeping the noise down is hard. Might make sense to jerry-rig something similar that only updates once every three months. Would that be useful?
Maintenance PR for applying @alanshaw's changes as described here https://github.com/orbitdb/ipfs-log/issues/183
Updates:
ipfs
to~0.33.0
datastore-level
to^0.9.0
ipfs-repo
to^0.24.0
Next Steps (after this PR)
npm audit fix
and compare resultsResolves #183