Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update node jose #12

Merged
merged 2 commits into from
Jan 4, 2022
Merged

Update node jose #12

merged 2 commits into from
Jan 4, 2022

Conversation

jportner
Copy link
Contributor

@jportner jportner commented Dec 28, 2021

Re-submitting #11.

Resolves #10.

This PR updates the node-jose dependency from version 1.1.0 to 2.0.0.
That removes support for Node 6 and Node 8, but I don't think we ever claimed / intended to support those.

  • If we do want to support Node 6/8, we can upgrade to node-jose 1.1.4 instead to resolve the linked issue.
  • If that is the case, we should explicitly mention somewhere what version(s) of Node that we support.

@cla-checker-service
Copy link

cla-checker-service bot commented Dec 28, 2021

💚 CLA has been signed

@jportner
Copy link
Contributor Author

jportner commented Dec 28, 2021

(continuing from #11 (comment))

Fixed now!

@jportner jportner changed the title Update node jose again Update node jose Dec 28, 2021
@jportner
Copy link
Contributor Author

Rethinking this:

That removes support for Node 6 and Node 8, but I don't think we ever claimed / intended to support those.

  • If we do want to support Node 6/8, we can upgrade to node-jose 1.1.4 instead to resolve the linked issue.
  • If that is the case, we should explicitly mention somewhere what version(s) of Node that we support.

The only other non-dev dependency this package has is @elastic/node-crypto, and that explicitly supports Node 8.
So, there could be consumers out there who are using this in Node 8.

Perhaps, in the spirit of SemVer, this PR should bump this package's version to 2.0.0 and we should state that Node 8 is not supported anymore.

WDYT?

@Bamieh
Copy link
Member

Bamieh commented Jan 4, 2022

@jportner I guess it makes sense to bump it to 2.0.0 to be safe.

@Bamieh Bamieh merged commit 9bbb060 into elastic:master Jan 4, 2022
This was referenced Jan 4, 2022
@jportner jportner deleted the update-node-jose-again branch January 26, 2022 15:17
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.

Buggy version of node-jose breaks node-forge for other consumers
2 participants