upgrade dependencies #489
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/spee.ch#489
Loading…
Reference in a new issue
No description provided.
Delete branch "dependencies-upgrade"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR brings in upgrades to the packages used in the project as github is warning about vulnerabilities.
In more detail, the following upgrades were performed:
No tests were run, some major upgrades might not be compatible at all. I'd like the help of someone actively developing the project to take a look
thanks @nikooo777 I'll test
I tested this today. It seems to be working, except the winston logger is throwing a warning
Attempt to write logs with no transports
when logging. This doesn't seem to be an issue with winston, because it happens when I downgraded it back to2.3.1
as well. I'm not sure what change created this. I'd like to merge thelbryio/www.spee.ch
repo with this repo before debugging this, as it may have to do with the relative paths used in that repo to get resources from this package.Absolutely! let me know if you want to do a session together so we can debug it with 4 eyes :)
@nikooo777, are you familiar with https://github.com/greenkeeperio/greenkeeper ?
I am not, but that looks like a nice tool we could implement! As long as it doesn't automatically merge the new dependencies though.
Looks good after the log is resolved, likely something simple