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

Automated backport of #3317: Fix vulnerabilities in go-git #3318

Conversation

vthapar
Copy link
Contributor

@vthapar vthapar commented Jan 8, 2025

Backport of #3317 on release-0.19.

#3317: Fix vulnerabilities in go-git

For details on the backport process, see the backport requests page.

@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr3318/vthapar/automated-backport-of-#3317-upstream-release-0.19
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

Bump to go-git/v5.13.0

Signed-off-by: Maayan Friedman <[email protected]>
@vthapar vthapar force-pushed the automated-backport-of-#3317-upstream-release-0.19 branch from 564f77f to b0a5d7c Compare January 8, 2025 10:27
@vthapar
Copy link
Contributor Author

vthapar commented Jan 8, 2025

Closing this coz incomplete merge conflict resolution.

@vthapar vthapar closed this Jan 8, 2025
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr3318/vthapar/automated-backport-of-#3317-upstream-release-0.19]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants