Skip to content

Update stacked: lz4 1.11.0 -> 1.11.1 - #1524

Queued
gominimal-pkgmgr-mgr[bot] wants to merge 1 commit into
mainfrom
update-stacked-2026-11-14-69132310
Queued

gominimal-pkgmgr-mgr[bot] wants to merge 1 commit into
mainfrom
update-stacked-2026-11-14-69132310

Conversation

@gominimal-pkgmgr-mgr

Copy link
Copy Markdown
Contributor

Update base-soup (1 package)

Note

lz4 declares replace_on_cycle in build.ncl, so they take part in
the toolchain rebuild graph and one hash change cascades through the
set. Bundling lands the cascading rebuild as a single unit, even when
only one package is bumping, which avoids back-to-back full rebuilds
from singleton PRs.

Pkgscan: clean across every scanned bundle member — diffs against prior versions surfaced no newly-introduced suspicious patterns.

Note

Build risk — 5 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
lz4 5 — file, postgres, rizin, rsync, zstd

Summary

Package Old New Source
lz4 1.11.0 1.11.1 github:lz4/lz4:release-asset:operator-pinned

Per-package details

lz4 1.11.0 → 1.11.1
  • SHA256: 247e5fa64da5f7b7... → 683fed08a844ad01...
  • Size: 546 KB → 553 KB
  • Source: gs://minimal-staging-archives/lz4-1.11.0.tar.gz → gs://minimal-staging-archives/lz4-1.11.1.tar.gz
  • Released: 3 days ago (2026-11-11)
  • 🔒 TLS: github.com — Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (root c90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519 ⇒ release-assets.githubusercontent.com — YR1 → Root YR → ISRG Root X1 (root 96bcec06264976f3…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519

License

  • Upstream 1.11.0 → 1.11.1: unchanged, license files byte-identical (LICENSE)
  • Declared license_spdx: BSD-2-Clause AND GPL-2.0-or-later, not checked against upstream: the detector couldn't identify the new release's license files with confidence

Created by pkgmgr

@gominimal-pkgmgr-mgr
gominimal-pkgmgr-mgr Bot requested a review from a team as a code owner November 14, 2026 20:16
@coderabbitai

coderabbitai Bot commented Nov 14, 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

@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.

Scope matches the title. The diff changes the version string, the source sha256, and the two hardcoded paths in build.sh. Clobber none. git log on packages/lz4 shows the gen-13 bootstrap pin (#1242) and the 1.11.0 bump (#1385). The diff keeps both, and replace_on_cycle is unchanged. Correctness The version binding, the %{version} URL and the build.sh paths agree on 1.11.1. Secrets: none in the diff. Not checked The gs://minimal-staging-archives tarball and its hash need a fetch from a private bucket. I did not run a build. So I did not confirm that the 1.11.0 workarounds in build.sh are still necessary on 1.11.1: the CPPFLAGS=-DNDEBUG export and the install-only target. Their comments (lines 16-24, outside the diff) still name 1.11.0. Re-check them against the 1.11.1 Makefile, then update or remove them.

Comment thread packages/lz4/build.sh
tar -xof lz4-1.11.0.tar.gz
cd lz4-1.11.0
tar -xof lz4-1.11.1.tar.gz
cd lz4-1.11.1

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.

low · build.sh hardcodes 1.11.1 in a second place. Each bump must edit it beside the version binding in build.ncl, and this PR shows that. AGENTS.md asks for build_args = { include version } and $MINIMAL_ARG_VERSION. With that change, a bump is one edit in build.ncl. Add build_args = { include version }, to build.ncl and use lz4-$MINIMAL_ARG_VERSION here. This is one of 35 build.sh files with a hardcoded tarball name, and 170 use the variable. So the fix is local, but the pattern repeats.

@bryan-minimal
bryan-minimal added this pull request to the merge queue Nov 18, 2026
Any commits made after this event will not be merged.
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.

1 participant