Merge pull request #5376 from kolyshkin/seccomp-261

build: bump libseccomp to v2.6.1

Author: AkihiroSuda

CHANGELOG.md

@@ -10,6 +10,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - The poststart hooks are now executed after starting the user-specified
   process, fixing a runtime-spec conformance issue. (#4347, #5186)
 
+### Changed ###
+- Updated builds to libseccomp v2.6.1. (#5376)
+
 ## [1.5.0] - 2026-06-19
 
 > Why do we even have that lever?!

Dockerfile

@@ -1,6 +1,6 @@
 ARG GO_VERSION=1.25
 ARG BATS_VERSION=v1.12.0
-ARG LIBSECCOMP_VERSION=2.6.0
+ARG LIBSECCOMP_VERSION=2.6.1
 ARG LIBPATHRS_VERSION=0.2.5
 
 FROM golang:${GO_VERSION}-trixie

script/build-seccomp.sh

@@ -10,6 +10,7 @@ declare -A SECCOMP_SHA256=(
 	["2.5.5"]=248a2c8a4d9b9858aa6baf52712c34afefcf9c9e94b76dce02c1c9aa25fb3375
 	["2.5.6"]=04c37d72965dce218a0c94519b056e1775cf786b5260ee2b7992956c4ee38633
 	["2.6.0"]=83b6085232d1588c379dc9b9cae47bb37407cf262e6e74993c61ba72d2a784dc
+	["2.6.1"]=501f66c667225d53791b97e1d7cf85ab764c297d04881f60f38f451c4b0ee1be
 )
 
 # Due to libseccomp being LGPL we must include its sources,

script/release_build.sh

@@ -19,7 +19,7 @@ set -e
 ## --->
 # Project-specific options and functions. In *theory* you shouldn't need to
 # touch anything else in this script in order to use this elsewhere.
-: "${LIBSECCOMP_VERSION:=2.6.0}"
+: "${LIBSECCOMP_VERSION:=2.6.1}"
 : "${LIBPATHRS_VERSION:=0.2.5}"
 project="runc"
 root="$(readlink -f "$(dirname "${BASH_SOURCE[0]}")/..")"