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

Feature/CVE 2023 45727 #150

Merged
merged 2 commits into from
Dec 4, 2024
Merged

Feature/CVE 2023 45727 #150

merged 2 commits into from
Dec 4, 2024

Conversation

PiranhaSa
Copy link
Contributor

Detction with version , I did exclude v5 because there isn't a clear way to know the specific version , I'm only able to see v.5 but I can't know if it's v5.63 or v5.62

@PiranhaSa PiranhaSa requested a review from a team as a code owner December 4, 2024 11:40
Copy link

codecov bot commented Dec 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.23%. Comparing base (eaa78cd) to head (ec4065c).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #150      +/-   ##
==========================================
+ Coverage   96.21%   96.23%   +0.02%     
==========================================
  Files         194      196       +2     
  Lines        6981     7020      +39     
==========================================
+ Hits         6717     6756      +39     
  Misses        264      264              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@benyissa benyissa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we can't detect v5.63 or v5.62, I think it's better to include v5 as a potential option rather than hiding it.

@3asm 3asm merged commit 72fae6f into main Dec 4, 2024
5 checks passed
@3asm 3asm deleted the feature/cve-2023-45727 branch December 4, 2024 13:16
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.

3 participants