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 dependencies version #79

Open
13 of 15 tasks
RainbowMango opened this issue Jun 6, 2022 · 11 comments · Fixed by #82 or #141
Open
13 of 15 tasks

Update dependencies version #79

RainbowMango opened this issue Jun 6, 2022 · 11 comments · Fixed by #82 or #141
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@RainbowMango
Copy link
Member

RainbowMango commented Jun 6, 2022

What would you like to be added:
Update the dependencies version(in both package-lock.json and yarn.lock) due to security concerns:

  • Upgrade trim to version 0.0.3 or later
  • Upgrade browserslist to version 4.16.5 or later
  • Upgrade dns-packet to version 1.3.2 or later
  • Upgrade ws to version 7.4.6 or later
  • Upgrade normalize-url to version 4.5.1 or later
  • Upgrade tar to version 6.1.9 or later.
  • Upgrade path-parse to version 1.0.7 or later (update package.json #380, @samzong)
  • Upgrade nth-check to version 2.0.1 or later
  • Upgrade follow-redirects to version 1.14.8 or later
  • Upgrade node-fetch to version 2.6.7 or later
  • Upgrade ansi-regex to version 5.0.1 or later.
  • Upgrade minimist to version 1.2.6 or later.
  • Upgrade cross-fetch to version 3.1.5 or later.
  • Upgrade ansi-regex to version 3.0.1 or later.
  • Upgrade got to version 11.8.5 or later.

Why is this needed:

@RainbowMango RainbowMango added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 6, 2022
@RainbowMango
Copy link
Member Author

I guess if we upgrade the docusaurus to a new version might solve all issues list on above.

cc @rgrupesh @Arhell

@rgrupesh
Copy link
Member

rgrupesh commented Jun 6, 2022

I guess if we upgrade the docusaurus to a new version might solve all issues list on above.

cc @rgrupesh @Arhell

Which version should we upgrade to?

@Arhell
Copy link
Member

Arhell commented Jun 6, 2022

I guess if we upgrade the docusaurus to a new version might solve all issues list on above.
cc @rgrupesh @Arhell

Which version should we upgrade to?

latest?

@RainbowMango
Copy link
Member Author

Yes, we can use the latest 2.0.0-beta.21.

@kevin-wangzefeng
Copy link
Member

As https://github.com/facebook/docusaurus/releases/tag/v2.0.1 is now available, we can upgrade to v2.0.1 as it's a more stable version

@Arhell
Copy link
Member

Arhell commented Aug 24, 2022

As https://github.com/facebook/docusaurus/releases/tag/v2.0.1 is now available, we can upgrade to v2.0.1 as it's a more stable version

i update all to latest version
PR #141

@RainbowMango
Copy link
Member Author

Hi @Arhell , Thanks for doing this. most of the dependencies are done by #156, but still have 4 left.

@samzong
Copy link
Member

samzong commented Jun 6, 2023

If possible, I would like to participate in the repair work here.

@RainbowMango
Copy link
Member Author

Sure, go ahead, appreciate it.
/assign @samzong

@samzong
Copy link
Member

samzong commented Jun 17, 2023

#380 upgrade path-parse to 1.0.7

@RainbowMango
Copy link
Member Author

Thanks @samzong . Only two alerts left now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants