-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Avoid using deprecated version of UUID #925
Comments
@ maintainers? |
Is there some reason this has not been addressed? toolkit/packages/cache/package.json Line 49 in 4573039
In other places Could this also be updated in https://github.com/actions/toolkit/blob/main/packages/cache/package.json to avoid the deprecation warning?
|
|
Could this issue please be addressed? |
|
I also ran into this message when using |
FWIW the dep isn't even needed; all uses of the library in the repo are just generating UUIDv4s, and Node has had |
Do the packages |
👋 Sorry for the delay, this issue got lost on our backlog and we can definitely do better here. I'll follow up tomorrow on updating the UUID we use, whether that's updating the |
#1824 will remove this direct dependency, we'll need another update for any packages that have an indirect dependency on |
Are you expecting to release an update anytime soon for |
There will be a new update soon, the changes broke users on Node 18 - #1841 |
|
All versions of the UUID npm package < 7 have been deprecated due to a weakness in
Math.random()
. There are two packages in this repository that use the deprecated version.Any downstream package that depends on these packages will include the following line in their
package-lock.json
:Can you upgrade node UUID to the latest released version? Happy to submit a PR to help you out.
The text was updated successfully, but these errors were encountered: