Skip to content

go.mod - update to elastic/go-seccomp-bpf v1.5.0 #41559

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

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Nov 7, 2024

Proposed commit message

This release updates the syscall tables based on Linux v6.11.

https://github.com/elastic/go-seccomp-bpf/releases/tag/v1.5.0

https://github.com/elastic/go-seccomp-bpf/compare/v1.4.0..v1.5.0

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 7, 2024
Copy link
Contributor

mergify bot commented Nov 7, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @andrewkroh? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Nov 7, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Nov 7, 2024
@andrewkroh andrewkroh marked this pull request as ready for review November 7, 2024 20:31
@andrewkroh andrewkroh requested a review from a team as a code owner November 7, 2024 20:31
Copy link
Contributor

mergify bot commented Nov 26, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-go-seccomp-bpf-1.5 upstream/update-go-seccomp-bpf-1.5
git merge upstream/main
git push upstream update-go-seccomp-bpf-1.5

@andrewkroh andrewkroh force-pushed the update-go-seccomp-bpf-1.5 branch 2 times, most recently from 9fe1111 to fe286d2 Compare November 26, 2024 22:30
@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Nov 27, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 27, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@andrewkroh andrewkroh merged commit 8d1a27e into elastic:main Nov 27, 2024
141 checks passed
mergify bot pushed a commit that referenced this pull request Nov 27, 2024
pierrehilbert pushed a commit that referenced this pull request Nov 27, 2024
This release updates the syscall tables based on Linux v6.11.

https://github.com/elastic/go-seccomp-bpf/releases/tag/v1.5.0
(cherry picked from commit 8d1a27e)

Co-authored-by: Andrew Kroh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants