Update jwk-to-pem to the latest version 🚀

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.0 of jwk-to-pem was just published.

Dependency	jwk-to-pem
Current Version	1.2.6
Type	dependency

The version 2.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of jwk-to-pem.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 11 commits.

• c2251f6 package: bump v2.0.0
• 7e6e5c8 package: cleanup
• eac126c Merge pull request #26 from omsmith/pkcs8
• aaec638 ec: pkcs8 private
• 8c9a33c ec: pkcs8 pubkeys
• d6279a1 rsa: pkcs8 private
• 56e00da rsa: pkcs8 public keys
• 4e3bb5e build, deploy: update node versions
• d586c21 chore: ignore package-lock
• 4b10d76 Merge pull request #25 from omsmith/OWNERS
• 842d485 meta: add myself as initial owner

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[coveralls]

Pull Request Test Coverage Report for Build 258

• 0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.029%

---

Totals
Change from base Build 254:	0.0%
Covered Lines:	646
Relevant Lines:	675

---

💛 - Coveralls