-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Explicitly import crypto
#1842
Explicitly import crypto
#1842
Conversation
Were these manual tests? Anything we can easily automate to prevent future accidental breakages like this? |
We can run tests against other Node versions besides the current support action Node version. I've validated that this catches the issue described in #1841 - #1843. In the future we should be clear about what Node versions we support for the toolkit, but until then I think it's reasonable to validate that the toolkit at least works with what users currently expect. |
##### [`v1.11.1](https://github.com/actions/toolkit/blob/HEAD/packages/core/RELEASES.md#1111) - Fix uses of `crypto.randomUUID` on Node 18 and earlier [#1842](actions/toolkit#1842)
##### [`v1.11.1](https://github.com/actions/toolkit/blob/HEAD/packages/core/RELEASES.md#1111) - Fix uses of `crypto.randomUUID` on Node 18 and earlier [#1842](actions/toolkit#1842)
#1841
crypto
has to be explicitly imported in versions before Node 19, so #1824 broke using these packages.I've validated that importing
crypto
works as expected on Node 16, 18, and 20:#1841 (comment)