Repository navigation
Update stacked: 2 packages - #1446
Merged
Merged
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
bryan-minimal
approved these changes
Nov 12, 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
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 stacked (2 packages)
Note
A convenience bundle of independent updates, chosen with
--stacked. None of these packages declaresreplace_on_cycle,so no hash change here cascades through the others; they ship
together only so one review and one build run cover the set.
Note
Build risk — 17 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.
gitbun,capy,claude-code,drift,emacs-config-dev1,fish,foundationdb,git-lfs(+9 more)Summary
2.56.02.56.1github:git/git:tag:operator-pinned0.167.00.167.1github:openai/codex:operator-pinnedWarning
1 known vulnerabilities still affect this bundle after update. Run
pkgmgr vulnsfor details.Per-package details
git 2.56.0 → 2.56.126c56c296b38c069...→f0b0bf89264b9bd2...gs://minimal-staging-archives/git-2.56.0.tar.xz→gs://minimal-staging-archives/git-2.56.1.tar.xzGPL-2.0-only(source: tarball)www.kernel.org— GlobalSign Atlas R46 DV TLS CA 2026 Q3 → GlobalSign Root R46 (root4fa3126d8d3a11d1…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519License
2.56.0→2.56.1: unchanged, license files byte-identical (COPYING)license_spdx:GPL-2.0-onlyagrees with the new release (GPL-2.0-only)codex 0.167.0 → 0.167.1313e49728fba6c3d...→c1c35ded9cf1b775...https://github.com/openai/codex/archive/refs/tags/rust-v0.167.0.tar.gz→https://github.com/openai/codex/archive/refs/tags/rust-v0.167.1.tar.gzApache-2.0(source: GitHub + tarball)github.com— Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (rootc90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519 ⇒codeload.github.com— Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (rootc90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519Carried patches vs 0.167.1
Each
| Localpatch was dry-run against the extracted 0.167.1 tree, forward and reverse, both with exact context (patch -N -F0,patch -R -F0). Only a patch that reverse-applies WHOLE is treated as upstream; a partial match is a conflict, and one that applies forward only with fuzz is reported as such.openssl-4-openssl-sys-lock.patch— still applies forward to 0.167.1. Security floors: met by 0.167.1's own lock.License
0.167.0→0.167.1: unchanged, license files byte-identical (LICENSE,docs/license.md)license_spdx:Apache-2.0agrees with the new release (Apache-2.0)Created by pkgmgr