build(deps): bump kata-sys-util from 3.8.0 to 3.9.0 in /src/enclave-agent

[dependabot]

Bumps kata-sys-util from 3.8.0 to 3.9.0.

Release notes

Sourced from kata-sys-util's releases.

Kata Containers 3.9.0

Survey

Please take the Kata Containers survey:

• https://openinfrafoundation.formstack.com/forms/kata_containers_user_survey

This will help the Kata Containers community understand:

• how you use Kata Containers
• what features and improvements you would like to see in Kata Containers

Libseccomp Notices

The kata-agent binaries inside the Kata Containers images provided with this release are statically linked with the following GNU LGPL-2.1 licensed libseccomp library.

• libseccomp

The kata-agent uses the libseccomp v2.5.5 which is not modified from the upstream version. However, in order to comply with the LGPL-2.1 (§6(a)), we attach the complete source code for the library.

Kata Containers builder images

• agent (on all its different flavours): quay.io/kata-containers/builders:agent-2b2d0f738-107265821-x86_64
• Kernel (on all its different flavours): quay.io/kata-containers/builders:kernel-c95ae5a50-x86_64
• OVMF (on all its different flavours): quay.io/kata-containers/builders:ovmf-c99ba42d6-x86_64
• QEMU (on all its different flavurs): quay.io/kata-containers/builders:qemu-74662a072-x86_64
• shim-v2: quay.io/kata-containers/builders:shim-v2-go-1.22.2-rust-1.75.0-25c784c56-x86_64
• tools: quay.io/kata-containers/builders:tools-593cbb871-eb1227f47-1597f8ba0-69535e545-x86_64
• virtiofsd: quay.io/kata-containers/builders:virtiofsd-1.72.0-musl-c99ba42d6-x86_64

Installation

Follow the Kata installation instructions.

What's Changed

• genpolicy: deny UpdateEphemeralMountsRequest by @​Redent0r in kata-containers/kata-containers#9911
• metrics: Remove unused variable in openvino script by @​GabyCT in kata-containers/kata-containers#10198
• kata-deploy: Rework the logic a little bit by @​fidencio in kata-containers/kata-containers#10194
• ci: commit-message-check: Take re-revert into consideration by @​fidencio in kata-containers/kata-containers#10196
• agent: kill child process when console socket closed by @​soulfy in kata-containers/kata-containers#10141
• Revert "tests: add image check before running coco tests" by @​amshinde in kata-containers/kata-containers#10207
• tests: Fix k8s test issues on s390x by @​BbolroC in kata-containers/kata-containers#10202
• agent/config: Make CDH_API_TIMEOUT configurable by @​BbolroC in kata-containers/kata-containers#10199
• kata-manager: Avoid docker rate-limit by @​fidencio in kata-containers/kata-containers#10209

... (truncated)

Changelog

Sourced from kata-sys-util's changelog.

How to do a Kata Containers Release

This document lists the tasks required to create a Kata Release.

Requirements

• GitHub permissions to run workflows.

Versioning

The Kata Containers project uses semantic versioning for all releases. Semantic versions are comprised of three fields in the form:

MAJOR.MINOR.PATCH

When MINOR increases, the new release adds new features but without changing the existing behavior.

When MAJOR increases, the new release adds new features, bug fixes, or both and which changes the behavior from the previous release (incompatible with previous releases).

A major release will also likely require a change of the container manager version used, -for example Containerd or CRI-O. Please refer to the release notes for further details.

Important : the Kata Containers project doesn't have stable branches (see this issue for details). Bug fixes are released as part of MINOR or MAJOR releases only. PATCH is always 0.

Release Process

Bump the VERSION and Chart.yaml file

When the kata-containers/kata-containers repository is ready for a new release, first create a PR to set the release in the VERSION file and update the version and appVersion in the Chart.yaml file and have it merged.

Lock the main branch

In order to prevent any PRs getting merged during the release process, and slowing the release process down, by impacting the payload caches, we have recently trailed setting the main branch to read only whilst the release action runs.

[!NOTE] Admin permission is needed to complete this task.

Check GitHub Actions

We make use of GitHub actions in the

... (truncated)

Commits

• cdaaf70 Merge pull request #10334 from emanuellima1/bump-version
• a6ee15c release: Bump VERSION to 3.9.0
• e9593b5 Merge pull request #10234 from pmores/add-support-for-disabled-guest-selinux
• 4d11fec Merge pull request #10274 from ajaypvictor/remote_image-os_types
• 3d5f48e Merge pull request #10283 from alexman-stripe/alexman-stripe/fix-kata-shim-no...
• 5e5eb97 runtime-rs: handle disabled guest selinux in virtiofsd
• 8c92f3b runtime-rs: enable/disable selinux in guest based on disable_guest_selinux
• 204ee21 runtime-rs: handle disabled guest selinux in OCI spec
• eb1227f runtime-rs: parse the disable_guest_selinux config key
• 8789551 Merge pull request #10333 from fidencio/topic/ci-bump-ubuntu-20.04-runners-to...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)