Skip to content

Update stacked: 7 packages - #984

Merged
bryan-minimal merged 11 commits into
mainfrom
update-stacked-2026-10-22-4c9ef9b9
Oct 23, 2026
Merged

bryan-minimal merged 11 commits into
mainfrom
update-stacked-2026-10-22-4c9ef9b9

Conversation

@gominimal-pkgmgr-mgr

@gominimal-pkgmgr-mgr gominimal-pkgmgr-mgr Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Update stacked (7 packages)

vim 9.2.1225, z3 5.3.1, xh 0.26.3, yq 4.54.1, zizmor 1.31.1, wrangler 4.151.3, xorgproto 2026.1.

Important

Revised after review. zig 0.17.0 and zls 0.17.0 are out of this PR: zig 0.17.0 links
LLVM 22 and pkgs ships llvm 21.1.8, so it cannot build (zls needs zig 0.17.0). Follow-up:
#996 (llvm 22, then zig + zls). The original head's build-bot run failed on zig on both
arches within seconds and aborted the run, so none of the other members built.

These 7 are an independent --stacked set from the Slack picker, not a replace_on_cycle
base-soup bundle: none of them declares replace_on_cycle. The bot's generic bundling
note claimed otherwise; that's a pkgmgr wording bug, being fixed there.

xh: the CVE-2026-111943 lock patch stays dropped (0.26.3's upstream Cargo.lock already
has rustls-webpki 0.103.16 and webpki-root-certs 1.0.10), but the fail-closed grep guard in
build.sh is back as a regression check. It requires rustls-webpki to be present and
rejects any pre-fix 0.103.x / 1.0.x, without an exact pin, so later bumps don't trip it.
zizmor: keeps its lock patch (1.31.1's lock has 0.103.13).

Verified in a fresh remote session at this head: --rebuild of xh and zizmor (both compile
rustls-webpki 0.103.16; zizmor's cargo build --locked passes with the patch), and
min check --packages xh zizmor passes everything with no Skip, standalone tests included.

Warning

1 requested member did NOT ship — each needs separate follow-up.
A member is dropped when it fails to update, has its gs:// mirror
withheld by the scan gate, or is peeled to keep the shipped set a
closed dependency closure. Reasons are abbreviated — the full
diagnostics ride the Slack thread and the run's logs.

Package Old Target Why
verus-latest 0.2026.10.04.426d8b0 0.2026.10.18.7d82994 update failed: [verus-latest] multi-arch build.
Pkgscan: 2 below-threshold signals across bundle members (all Info severity, risk score 0.2). Demoted in benign contexts (test fixtures, CI workflow setup); expand for details.
Package Severity File Line Capability (MBC) Pattern
xorgproto INFO xorgproto (upstream release) 0 metadata/recent-bump recency NOT evaluated — no release date from the version source

Note

Build risk — 45 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.

Bundle member Dependents
xorgproto 41 — icedtea-7, icedtea-8, libglvnd, libice, libsm, libx11, libxau, libxcb (+33 more)
zig 3 — dev-language-servers, fx, herdr
zls 1 — dev-language-servers

Summary

Package Old New Source
xorgproto 2025.1 2026.1 override:xorgproto:operator-pinned
vim 9.2.1202 9.2.1225 github:vim/vim:tag:operator-pinned
wrangler 4.135.0 4.151.3 github:cloudflare/workers-sdk:operator-pinned
xh 0.26.2 0.26.3 github:ducaale/xh:operator-pinned
yq 4.53.6 4.54.1 github:mikefarah/yq:operator-pinned
z3 5.1.0 5.3.1 github:Z3Prover/z3:operator-pinned
zizmor 1.30.1 1.31.1 github:zizmorcore/zizmor:operator-pinned

Per-package details

xorgproto 2025.1 → 2026.1
  • SHA256: 56898c716c0578df... → f9bfe4a9ed8c8ab9...
  • Size: 767 KB → 772 KB
  • Source: gs://minimal-staging-archives/xorgproto-2025.1.tar.xz → gs://minimal-staging-archives/xorgproto-2026.1.tar.xz
  • Released: unknown (non-GitHub source or tag-only fallback)
  • License: (BSD-2-Clause AND HPND AND HPND-sell-variant AND ICU AND MIT AND MIT-open-group AND SGI-B-2.0 AND SMLNJ AND X11 AND X11-swapped) (source: tarball)
vim 9.2.1202 → 9.2.1225
  • SHA256: 9e97414b85bdcb2d... → 797cf32f4a54a0a9...
  • Size: 20.3 MB → 20.3 MB
  • Source: gs://minimal-staging-archives/vim-9.2.1202.tar.gz → gs://minimal-staging-archives/vim-9.2.1225.tar.gz
  • Released: 1 days ago (2026-10-21)
  • License: Vim (source: GitHub + tarball)
wrangler 4.135.0 → 4.151.3
  • SHA256: →
  • Size: 0 B
  • Source: npm:wrangler@4.135.0 → npm:wrangler@4.151.3
  • Released: unknown (non-GitHub source or tag-only fallback)
xh 0.26.2 → 0.26.3
  • SHA256: 61a88a5b3beac225... → 8c54c7e8e878600d...
  • Size: 334 KB → 334 KB
  • Source: gs://minimal-staging-archives/ducaale/xh/v0.26.2.tar.gz → gs://minimal-staging-archives/ducaale/xh/v0.26.3.tar.gz
  • Released: 1 days ago (2026-10-21)
  • License: MIT (source: GitHub + tarball)

Carried patches vs 0.26.3

Each | Local patch was dry-run against the extracted 0.26.3 tree: forward as build.sh applies it (patch -N), and reverse with exact context (patch -R -F0). Only a patch that reverse-applies WHOLE is treated as upstream; a partial match is a conflict.

  • Removed cve-2026-111943-webpki-lock.patch — reverse-applies to 0.26.3; already upstream. Dropped its build.ncl entry, its build.sh apply line, its build.sh lockfile guard, the comments above each, and the file. Security floors: met by 0.26.3's own lock.

No carried patch remains, so patch was dropped from build_deps (and its import, when unused). Regression tests that guard a removed fix stay.

yq 4.53.6 → 4.54.1
  • SHA256: 132a28a669526f99... → 0cec36e7035dd56c...
  • Size: 384 KB
  • Source: https://github.com/mikefarah/yq/archive/refs/tags/v4.53.6.tar.gz → https://github.com/mikefarah/yq/archive/refs/tags/v4.54.1.tar.gz
  • Released: 23 days ago (2026-09-29)
  • License: MIT (source: GitHub + tarball)
z3 5.1.0 → 5.3.1
  • SHA256: c433e1add0431c5e... → c007089dd8d92298...
  • Size: 7.9 MB
  • Source: https://github.com/Z3Prover/z3/archive/refs/tags/z3-5.1.0.tar.gz → https://github.com/Z3Prover/z3/archive/refs/tags/z3-5.3.1.tar.gz
  • Released: 6 days ago (2026-10-15)
  • License: MIT (source: tarball)
zizmor 1.30.1 → 1.31.1
  • SHA256: 3224fd5b49b77b2e... → 9e976cc981bb9b0b...
  • Size: 798 KB
  • Source: https://github.com/zizmorcore/zizmor/archive/refs/tags/v1.30.1.tar.gz → https://github.com/zizmorcore/zizmor/archive/refs/tags/v1.31.1.tar.gz
  • Released: 6 days ago (2026-10-15)
  • License: MIT (source: GitHub + tarball)

Carried patches vs 1.31.1

Each | Local patch was dry-run against the extracted 1.31.1 tree: forward as build.sh applies it (patch -N), and reverse with exact context (patch -R -F0). Only a patch that reverse-applies WHOLE is treated as upstream; a partial match is a conflict.

  • Kept cve-2026-111943-webpki-lock.patch — still applies forward to 1.31.1. Security floors 1.31.1's own lock misses: rustls-webpki 0.103.13 < 0.103.16 (CVE-2026-111943 / RUSTSEC-2026-0382); webpki-root-certs 1.0.5 < 1.0.10 (CVE-2026-111943 / RUSTSEC-2026-0383).

Created by pkgmgr

@gominimal-pkgmgr-mgr
gominimal-pkgmgr-mgr Bot requested a review from a team as a code owner October 22, 2026 17:32
@coderabbitai

coderabbitai Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@norrietaylor norrietaylor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can't land as-is:

  1. zig 0.17.0 needs LLVM 22; the official 0.17.0 build links LLVM 22.1.8. pkgs has llvm 21.1.8 (packages/llvm/build.ncl:13), and zig's CMake needs the matching major, so this will fail to build. It takes zls with it, whose minimum_zig_version is 0.17.0. fx, herdr and dev-language-servers are also at risk, since zig breaks std between minors. Its post-build checks all show Skip.
  2. No minimal build ran on this head, so none of the 9 has been shown to build.
  3. The bundling reason doesn't hold. None of the 9 build.ncl files declares replace_on_cycle, so a zig failure blocks unrelated fixes: vim 9.2.1225's crash and overflow fixes, z3 5.3.1's soundness fix, and xh.

Suggestion: pull zig and zls out until llvm 22 is packaged, and land the other 7 once minimal build is green.

Per package:

  • I verified hashes by reproducing them from the upstream tags for zls, vim, xh, yq, z3 and zizmor. xorgproto matches staging only, and zig couldn't be verified.
  • xh: dropping the webpki lock patch is correct (0.26.3's lock already has 0.103.16), but I'd keep the fail-closed grep guards in build.sh as regression checks.
  • zizmor: the kept lock patch is still needed (1.31.1 has 0.103.13). Only a build will prove that --locked passes.

Generated by Claude Code

bryan-minimal and others added 2 commits October 22, 2026 16:39
…11943 lock guard

zig 0.17.0 links LLVM 22 and pkgs has llvm 21.1.8, so zig (and zls, whose
minimum_zig_version is 0.17.0) go back to main's versions until llvm 22 is
packaged. xh 0.26.3's upstream lock already carries rustls-webpki 0.103.16 and
webpki-root-certs 1.0.10, so the lock patch stays dropped, but the fail-closed
grep guard is restored as a regression check (presence + no pre-fix versions,
not an exact pin, so later bumps don't trip it).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bryan-minimal bryan-minimal changed the title Update stacked: 9 packages Update stacked: 7 packages Oct 22, 2026
@bryan-minimal

Copy link
Copy Markdown
Member

Thanks @norrietaylor. All three points held up; addressed in fa6792e, on top of a merge of main (340771d):

  1. zig 0.17.0 / LLVM 22: zig and zls are back to main's versions, so this is now 7 packages. Follow-up is llvm 22, then zig 0.17.0 + zls 0.17.0 (pulled from #984) #996: package llvm 22, then zig 0.17.0 + zls, then re-check fx, herdr and dev-language-servers.
  2. No minimal build: a build did run, but late. build-bot trusted the PR at 17:32Z, the run started at 22:03Z, and zig failed on both arches within seconds, which aborted the run before any other member built (run aa259806-ee84-4107-801b-d5f87bbc1d1b). The new head was trusted at 23:39Z and is queued; that run is the build of the 7.
  3. Bundling: you're right. These came from the Slack picker as an independent --stacked set, and none of them declares replace_on_cycle. The bot prints that note on every bundle regardless, which is a pkgmgr bug I'm reporting there. The PR body now says what this actually is.

Per package:

  • xh: the fail-closed grep guard is restored in build.sh as a regression check. It requires rustls-webpki to be present and rejects any pre-fix 0.103.x / 1.0.x, without pinning an exact version, so later bumps don't trip it. Tested against 0.26.3's real Cargo.lock: it passes, and it rejects three negative controls (rustls-webpki 0.103.13, webpki-root-certs 1.0.6, rustls-webpki missing).
  • zizmor: the lock patch is kept. In a fresh remote session at this head, --rebuild of xh and zizmor both compiled rustls-webpki 0.103.16, zizmor's cargo build --locked passed with the patch applied, and min check --packages xh zizmor passed everything with no Skip, standalone tests included.

nickel format --check, bash -n and mip dump (amd64 + arm64) are clean.

🤖 Generated with Claude Code

@bryan-minimal
bryan-minimal added this pull request to the merge queue Oct 23, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Oct 23, 2026
@bryan-minimal
bryan-minimal added this pull request to the merge queue Oct 23, 2026
Merged via the queue into main with commit b314a30 Oct 23, 2026
11 checks passed
@bryan-minimal
bryan-minimal deleted the update-stacked-2026-10-22-4c9ef9b9 branch October 23, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants