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

Upgrade crypto-js as the current have critical vulneravility #446

Closed
Altane-be opened this issue Nov 16, 2023 · 2 comments · Fixed by #451
Closed

Upgrade crypto-js as the current have critical vulneravility #446

Altane-be opened this issue Nov 16, 2023 · 2 comments · Fixed by #451
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. released type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@Altane-be
Copy link

Upgrage crypto-js to the 4.2.0 version.

@Altane-be Altane-be added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 16, 2023
@wangela
Copy link
Member

wangela commented Nov 16, 2023

If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.

@Altane-be Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

This is an automated message, feel free to ignore.

@wangela wangela added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed triage me I really want to be triaged. labels Dec 5, 2023
@googlemaps-bot
Copy link
Contributor

🎉 This issue has been resolved in version 1.0.30 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. released type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants