bombastictranz/CBL-Mariner

[bombastictranz]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

Change Log

• Change
• Change
• Change

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx

[codeautopilot]

PR summary

This PR introduces a number of changes, including security patches for various components, updates to package versions, and modifications to build scripts and utilities. It addresses several CVEs, updates the versions of bind, dnsmasq, kata-containers, libgit2, moby-compose, postgresql, unbound, and vim, and adds support for osslsigncode. The PR also includes changes to the build scheduler and result printing logic.

Suggestion

Overall, the PR seems comprehensive and addresses important security concerns. However, it's crucial to ensure that the updated versions and patches do not introduce any regressions or compatibility issues. It's recommended to perform thorough testing, including unit tests, integration tests, and end-to-end tests, to validate the changes. Additionally, it's important to review the dependency graph to ensure that all dependencies are correctly updated and there are no missing or conflicting versions. If any new features or configuration options are introduced, consider updating the documentation accordingly.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 110.38%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com