Repository navigation
Release SOW v0.6.1: Go 1.27.3 and dependency refresh - #2
Merged
Merged
Conversation
Vonng
marked this pull request as ready for review
October 22, 2026 12:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SOW v0.6.1 updates the build toolchain to Go 1.27.3 and refreshes runtime/test dependencies, including the AWS SDK, OpenPGP, compression, SQLite, Debian parsing, and the maintained YAML v3 module. The existing RPM parser hardening remains in place.
The patch also fixes malformed diagnostics caused by wrapping nil errors when rejecting invalid paths or OpenPGP armor in log export, RPM metadata generation, and workspace validation. It updates pinned CI/release tools and derives the CI snapshot version from the Makefile. Schema v13, the CLI, and the public repository layout are unchanged.
Local validation covers formatting, tidy, module verification, vet, staticcheck, deadcode, vulnerability reachability, RPM provenance and module tests, performance fixtures, GoReleaser configuration, and four-platform packaging. The 50,000-package YUM generation/signature/validation probe passed. Upgrade/rollback checks passed using the actual published v0.6.0 binary and a packaged v0.6.1 candidate.
For the final commit, CI passed quality checks, all Go unit tests, core race tests, clean source delivery, and four-platform packaging. Integration passed Ubuntu APT, EL8/9/10 DNF, and S3-compatible publication checks.
Parallel local macOS test/source-delivery runs encountered host-wide file descriptor exhaustion, including the old-version baseline. All 11 affected top-level unit tests passed when rerun separately on the final commit. The full local race run also reached its 45-minute limit; all 78 failed or remaining top-level race tests passed in a separate run on the final commit. The release uses the frozen commit and verified GitHub Actions artifacts.
Source vulnerability analysis reports no affected symbols or imported packages. Its module-level GO-2026-5932 notice concerns the unused
golang.org/x/crypto/openpgppackage. All four stripped release binaries trigger that notice in binary mode because govulncheck falls back to module-level precision without symbols. The four target import graphs exclude the legacy package, and a symbol-preserving control build reports zero affected symbols/packages.