Repository navigation
Update stacked: 2 packages - #698
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (3)
Included review availability: 2 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. 📝 WalkthroughWalkthroughPCRE2 was updated to 10.48. xz was updated to 5.8.4. The package checksums, xz build source path, working directory, and documentation path were updated to match. ChangesPackage version updates
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The package metadata and xz build paths are updated consistently, with no identified behavior or integration risk blocking merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
#698 (open since 2026-09-15, green, mergeable) sets pcre2 to 10.48 with the identical sha256 b6c68fdf, and also carries xz 5.8.3 -> 5.8.4. I cut this PR without checking the open queue first, which duplicated it and would have put two PRs on packages/pcre2/build.ncl. This PR is now openssl-only, which is its unique contribution. The pcre2 half of the hunk fix rides #698. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* openssl 3.6.4, pcre2 10.48 (11 CVEs, 2 Critical) openssl 3.6.3 matches 11 advisories — 2 Critical, 8 High, 1 Medium — and 3.6.4 (2026-08-25) fixes every one of them. Checked rather than assumed: the 11 CVEs the scan reports against 3.6.3 and the 11 CVEs named in the 3.6.4 release notes are the SAME SET, with nothing left over on either side. CVE-2026-63073 (9.8) CVE-2026-75803 (9.1) — Critical CVE-2026-14456 -14457 -18798 -54874 -54876 -63072 -63075 -63076 — High CVE-2026-63074 — Medium These are the same upstream vulnerabilities as gominimal#709, reaching us through a second packaging path: that PR fixes the copy inside the Alpine minirootfs, this fixes our own openssl package. One upstream advisory set, two places to bump. No version inversion and no jump to 4.x. OpenSSL 4.0.2 exists, but 3.6.4 is the fix for our line, and Alpine's 3.5.8 is the LTS-branch backport of the same CVEs — both lines were patched, we were one patch behind on ours. pcre2 10.47 -> 10.48 is bundled deliberately, not opportunistically. Its advisory yield is small and stated honestly: of pcre2's 7 advisories 10.48 clears exactly ONE, the LOW GHSA-q7rw-r7qq-2hx6. The HIGH OSV-2026-343 is commit-ranged and its fix commit e19e76ad is NOT an ancestor of the 10.48 tag (checked via compare: 10.48 is behind it), so 10.48 does not clear it. The remaining 5 have no upstream fix at all. The reason to bundle is the REBUILD, not the yield: openssl and pcre2 share git, nginx, wget and rizin, so one cascade instead of two. Both tarballs verified byte-identical against upstream before mirroring: openssl c6b94124bb76ac5f8aa80de121e0f922a93d3bbf1be478bd50ebc36a30dc1db1 pcre2 b6c68fdf6f3ac31388b50aa89ff0fc49c00c987c16e7b5146491d12003f2c8ed Not built locally: `min session activate` on this worktree hangs on exec, which is the symptom gominimal/inbox#693 / gominimal#690 describe. Left to CI's minimal-check, which does a real build. openssl has 38 direct importers and pcre2 7, so the rebuild is wide — worth a reviewer's eye on the cascade rather than mine alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * drop pcre2 from this PR — gominimal#698 already bumps it to 10.48 gominimal#698 (open since 2026-09-15, green, mergeable) sets pcre2 to 10.48 with the identical sha256 b6c68fdf, and also carries xz 5.8.3 -> 5.8.4. I cut this PR without checking the open queue first, which duplicated it and would have put two PRs on packages/pcre2/build.ncl. This PR is now openssl-only, which is its unique contribution. The pcre2 half of the hunk fix rides gominimal#698. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * ci: no-op commit to retrigger the build after the transport error --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Update base-soup (2 packages)
Note
These packages declare
replace_on_cyclein their build.ncl, sothey participate in the toolchain rebuild graph and one hash change
cascades through the set. Bundling ensures the cascading rebuild
lands as a single unit, even when only one package is bumping —
avoids back-to-back full rebuilds from singleton PRs.
Note
Build risk — 33 dependents across the tree. Package(s) that
build- or runtime-depend on a member of this bundle may need a rebuild,
or could FTBFS on an API/ABI change. Informational (not blocking) — a
heads-up for the reviewer on what this bump can ripple into.
xzbase,base-bootstrap,boost,cmake,coreutils,elfutils,ffmpeg,file(+18 more)pcre2fish,git,glib,grep,nginx,rizin,wgetSummary
5.8.35.8.4github:tukaani-project/xz:release-asset10.4710.48github:PCRE2Project/pcre2:release-assetVulnerabilities fixed (8)
(tukaani, xz)<= 5.8.3; <= 5.8.3(pcre, pcre2)>= 10.32, <= 10.47(pcre, pcre2)<= 10.47(pcre, pcre2)>= 10.30, <= 10.47(pcre, pcre2)>= 10.45, < 10.48; >= PCRE2(pcre, pcre2)<= 10.47(pcre, pcre2)>= 10.34, <= 10.47(pcre, pcre2)10.48Warning
1 known vulnerabilities still affect this bundle after update. Run
pkgmgr vulnsfor details.Per-package details
xz 5.8.3 → 5.8.4fff1ffcf2b0da84d...→4ce24038fd4221e0...gs://minimal-staging-archives/xz-5.8.3.tar.xz→gs://minimal-staging-archives/xz-5.8.4.tar.xz(0BSD AND GPL-2.0-only AND GPL-3.0-only AND LGPL-2.1-only)(source: tarball)pcre2 10.47 → 10.4847fe8c99461250d4...→b6c68fdf6f3ac313...gs://minimal-staging-archives/pcre2-10.47.tar.bz2→gs://minimal-staging-archives/pcre2-10.48.tar.bz2Created by pkgmgr
Summary by CodeRabbit