Skip to content

Conversation

@hiranya911
Copy link
Contributor

Resolves #905

Copy link
Member

@lahirumaramba lahirumaramba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Left one question

"jsonwebtoken": "8.1.0",
"node-forge": "0.7.4"
"jsonwebtoken": "^8.5.1",
"node-forge": "^0.7.6"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason why we wouldn't update this to most recent0.9.1?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I upgraded via npm update command, and this is what was automatically picked by NPM (possibly because 0.x versions are allowed to make breaking changes between minor releases). I will test 0.9.1 and upgrade in a separate PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. Thanks for checking!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update jsonwebtoken and node-forge

2 participants