Update stacked: 4 packages - #440
Merged
Merged
Conversation
twitchyliquid64
approved these changes
Jul 17, 2026
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
1 participant
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 (4 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.
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 (a survivor built against a dropped member's
old version would be a broken closure).
zsh5.95.9.2Warning
Pkgscan: 1 new signal introduced across bundle members.
Each member's diff was compared against its prior version. Review carefully — base-soup updates touch the toolchain core, so a malicious bump here has cascade-wide impact.
syft (upstream release)metadata/recent-bumpupstream release <48h agoSummary
1.14.41.15.2github:spiffe/spire:operator-pinned1.25.11.26.0github:starship/starship:operator-pinned6.177.1github:strace/strace:release-asset:operator-pinned1.42.41.48.0github:anchore/syft:operator-pinnedPer-package details
spire 1.14.4 → 1.15.2532ceb467da800e4...→0ef800257cc709db...https://github.com/spiffe/spire/archive/refs/tags/v1.14.4.tar.gz→https://github.com/spiffe/spire/archive/refs/tags/v1.15.2.tar.gzApache-2.0(source: GitHub + tarball)starship 1.25.1 → 1.26.0521306b14066ee7e...→8c95e8a6c596b29a...https://github.com/starship/starship/archive/refs/tags/v1.25.1.tar.gz→https://github.com/starship/starship/archive/refs/tags/v1.26.0.tar.gzISC(source: GitHub + tarball)strace 6.17 → 7.10a7c7bedc7efc076...→81743ecf2a5b4418...gs://minimal-staging-archives/strace-6.17.tar.xz→gs://minimal-staging-archives/strace-7.1.tar.xzsyft 1.42.4 → 1.48.08e84d456e253149d...→ee757ade3c9804fd...gs://minimal-staging-archives/anchore/syft/v1.42.4.tar.gz→gs://minimal-staging-archives/anchore/syft/v1.48.0.tar.gzApache-2.0(source: GitHub + tarball)Created by pkgmgr