Skip to content

Conversation

@yeikel
Copy link

@yeikel yeikel commented Jan 15, 2025

As per the pull request template

Please do not open a pull request to update only a version dependency. Existing process will perform
the upgrade every week. However, if the upgrade involves more changes (changes for deprecated API) then
your pull request is very welcome.

That however does not seem to be true for this component as it is quite outdated and is poisoning the project with various vulnerabilities such as

CVE-2024-26308
CVE-2024-25710

If this pull request is deemed as invalid even with the context above, I'd appreciate that the "process" is triggered and that this dependency is updated to fix the CVEs above

@yeikel
Copy link
Author

yeikel commented Jan 15, 2025

I saw #8338 after opening the pull request. Moving this as a draft for now waiting for clarify

@yeikel yeikel marked this pull request as draft January 15, 2025 23:54
@eddumelendez
Copy link
Member

Hi, thanks for raising the issue. I have shared before in one of the issues why we are not upgrading. We need to keep compatibility with other projects. Do you have proves that the CVEs are not false-positives?

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.

2 participants