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 gopkg.in/yaml.v3 version in go.mod #60

Merged
merged 1 commit into from
Dec 4, 2024
Merged

Update gopkg.in/yaml.v3 version in go.mod #60

merged 1 commit into from
Dec 4, 2024

Conversation

KshitijaKakde
Copy link
Contributor

@KshitijaKakde KshitijaKakde commented Dec 4, 2024

Description

Update gopkg.in/yaml.v3 version in go.mod

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #

Checklist:

  • I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
  • I have verified that new and existing unit tests pass locally with my changes
  • I have not allowed coverage numbers to degenerate
  • I have maintained at least 90% code coverage
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • Backward compatibility is not broken

Sorry, something went wrong.

Verified

This commit was signed with the committer’s verified signature.
@KshitijaKakde KshitijaKakde merged commit 322edd3 into main Dec 4, 2024
6 checks passed
@KshitijaKakde KshitijaKakde deleted the cve-fix branch December 4, 2024 06:12
@KshitijaKakde KshitijaKakde changed the title Fix CVE "CVE-2022-28948" Update gopkg.in/yaml.v3 version in go.mod Dec 4, 2024
@KshitijaKakde KshitijaKakde restored the cve-fix branch December 4, 2024 13:59
@KshitijaKakde KshitijaKakde deleted the cve-fix branch December 4, 2024 14:00
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.

None yet

4 participants