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

[1.22](backport #476) Update npcap to 1.80 #477

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Oct 15, 2024

Updates npcap to version 1.80. I'm reading the docs about updating npcap, and I don't quite get this comment:

Make sure the PR adding this is back-ported to the Go versions required by the Packetbeat CrossBuild target in the mage file

Is the go version in .go-version. linked to golang-crossbuild in some way? Do I need to backport this PR to some version that matches the go version used by beats?


This is an automatic backport of pull request #476 done by Mergify.

(cherry picked from commit 40bab45)
@mergify mergify bot requested a review from a team as a code owner October 15, 2024 18:15
@mergify mergify bot added the backport label Oct 15, 2024
@mergify mergify bot requested review from swiatekm and pchila October 15, 2024 18:15
@elasticmachine
Copy link

💚 Build Succeeded

cc @fearful-symmetry

@elasticmachine
Copy link

💚 Build Succeeded

cc @fearful-symmetry

@elasticmachine
Copy link

elasticmachine commented Oct 15, 2024

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @fearful-symmetry

@fearful-symmetry
Copy link
Contributor

@cmacknz can I get a review here? Also, it seems like I'll probably need a separate PR for 1.22.8?

@fearful-symmetry fearful-symmetry merged commit f564c53 into 1.22 Oct 16, 2024
10 checks passed
@fearful-symmetry fearful-symmetry deleted the mergify/bp/1.22/pr-476 branch October 16, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants