Repository navigation
8000
Update stacked: 9 packages - #665
Merged
Merged
Conversation
twitchyliquid64
approved these changes
Aug 31, 2026
twitchyliquid64
enabled auto-merge
August 31, 2026 20:32
Re-triggering the build to surface the current failure set. The `next` failure is understood (upstream node-lts 24.19.0 bundles an npm whose bundled dependency tree is self-inconsistent, breaking every `npm install` — #665 investigation); this re-run is to confirm nothing else has changed underneath it.
cvince
pushed a commit
to capysc/pkgs
that referenced
this pull request
Oct 2, 2026
…ak each other (gominimal#671) * fix(pnpm): depend on node, not node-lts — two npms in one sandbox breaks both pnpm only needs *a* node for its `#!/usr/bin/env node` shebang, but whichever one it names enters the closure of every package built with pnpm. `next` and `agent-browser` both declare `node` themselves, so each sandbox held TWO npm installs at the same paths. The sandbox hardlinks closure members first-writer-wins PER FILE, so /usr/lib/node_modules/npm came out a blend: minipass-flush/index.js from npm 11.17.0 (named `{ Minipass }` import) beside a nested minipass@3.3.6 from npm 11.11.1 (default export only). That tree never existed upstream and cannot load — `class Flush extends undefined` throws and every `npm install` dies. It broke `next` for two days and blocked gominimal#665, gominimal#667, gominimal#669 and gominimal#659. Verified: closure of next 75->74 and agent-browser 114->113 with node-lts gone, capy (the only other node-lts consumer) untouched; next, pnpm and agent-browser each build --rebuild clean and pass min check 15/15. Supersedes gominimal#670, whose fix was a no-op against node-lts's own output. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * refine: take only the node BINARY, not the whole package Review point from Bryan: pnpm should not be dictating a node version to its consumers at all. The spec language cannot express that today — RuntimeDep is BuildSpec | Subset | UpstreamPkg, all concrete, with no "consumer provides it" form — but `subsetOf` gets most of the way there. pnpm needs a node to interpret `#!/usr/bin/env node` and nothing else. Taking `subsetOf node ["node"]` instead of the whole package means pnpm can never contribute an npm tree to any closure, so the two-npms-merged-per-file failure is structurally impossible rather than merely absent from today's fleet. Residual, and worth stating: pnpm still names a version, so a future node-lts consumer adding pnpm would collide on the `node` binary. That is a much smaller failure than an unloadable module graph, and the real fix is a virtual/provided dependency in the spec language. Verified with the subset: next, pnpm and agent-browser all build --rebuild clean and pass min check, including pnpm's `missing runtime_deps` — which independently confirms the bare binary satisfies the shebang. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Update base-soup (9 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.
Pkgscan: 1 below-threshold signal across bundle members (all Info severity, risk score 0.1). Demoted in benign contexts (test fixtures, CI workflow setup); expand for details.
libaom (upstream release)metadata/recent-bumprecency NOT evaluated — no release date from the version sourceNote
Build risk — 6 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.
libpslcurl,wgeteslintdev-language-serversuvdiffoscopelibaomffmpeglibvpxffmpegSummary
0.23.20.23.3github:rockdaboot/libpsl:release-asset:operator-pinned10.9.010.9.1custom:https://registry.npmjs.org/eslint:operator-pinned0.12.50.12.7github:astral-sh/uv:operator-pinned0.0.60.0.8github:aymanbagabas/drift:operator-pinned3.14.13.15.0override:libaom:operator-pinned1.16.01.17.0github:webmproject/libvpx:tag:operator-pinned4.2.34.2.4github:helm/helm:operator-pinned0.4.70.4.12github:tontinton/maki:operator-pinned0.4.140.5.0github:j178/prek:operator-pinnedPer-package details
libpsl 0.23.2 → 0.23.3f2ea0e59bffb3659...→93941f85a1e7bd59...gs://minimal-staging-archives/libpsl-0.23.2.tar.gz→gs://minimal-staging-archives/libpsl-0.23.3.tar.gzMIT(source: tarball)eslint 10.9.0 → 10.9.1→npm:eslint@10.9.0→npm:eslint@10.9.1uv 0.12.5 → 0.12.7e349c9eb85876921...→4a0941ef8f8131bf...gs://minimal-staging-archives/uv-0.12.5.tar.gz→gs://minimal-staging-archives/uv-0.12.7.tar.gzMIT OR Apache-2.0(source: GitHub + tarball)drift 0.0.6 → 0.0.8814c26bcb8973423...→d17924f24b5df5fd...https://github.com/aymanbagabas/drift/archive/refs/tags/v0.0.6.tar.gz→https://github.com/aymanbagabas/drift/archive/refs/tags/v0.0.8.tar.gzMIT(source: GitHub + tarball)libaom 3.14.1 → 3.15.044bf90dbd23e734d...→ea08c38ecc078bc8...https://storage.googleapis.com/aom-releases/libaom-3.14.1.tar.gz→https://storage.googleapis.com/aom-releases/libaom-3.15.0.tar.gzBSD-2-Clause(source: tarball)libvpx 1.16.0 → 1.17.07a479a3c66b9f5d5...→1020f184046187ba...https://github.com/webmproject/libvpx/archive/refs/tags/v1.16.0.tar.gz→https://github.com/webmproject/libvpx/archive/refs/tags/v1.17.0.tar.gzBSD-3-Clause(source: GitHub + tarball)helm 4.2.3 → 4.2.49ca555fa3777082f...→f1a1aa56fff071cf...https://github.com/helm/helm/archive/refs/tags/v4.2.3.tar.gz→https://github.com/helm/helm/archive/refs/tags/v4.2.4.tar.gzApache-2.0(source: GitHub + tarball)maki 0.4.7 → 0.4.126337b40f5c1db69e...→024604df4bf2c0ac...https://github.com/tontinton/maki/archive/refs/tags/v0.4.7.tar.gz→https://github.com/tontinton/maki/archive/refs/tags/v0.4.12.tar.gzMIT(source: GitHub + tarball)prek 0.4.14 → 0.5.06f0d3615690382d4...→3a19e696c7b06942...gs://minimal-staging-archives/j178/prek/v0.4.14.tar.gz→gs://minimal-staging-archives/j178/prek/v0.5.0.tar.gzMIT(source: GitHub + tarball)Created by pkgmgr