From f3f17392e686d3492c10ded85e786809c44e508f Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 23:44:49 +0000 Subject: [PATCH 1/2] chore(deps): update dependency kernel-longterm-6.18 to v6.18.50 --- configs/fragments/de10nano.fragment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/fragments/de10nano.fragment b/configs/fragments/de10nano.fragment index 8cde3d12..8225756a 100644 --- a/configs/fragments/de10nano.fragment +++ b/configs/fragments/de10nano.fragment @@ -27,7 +27,7 @@ BR2_GLOBAL_PATCH_DIR="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/patches" # --- Kernel stanza (docs/buildroot-config.md ยง3.4) --- # Renovate bumps the version line (renovate.json, kernel-longterm-6.18); # the tarball hash follows via .github/workflows/renovate-hash-sync.yml. -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.49" +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.50" BR2_LINUX_KERNEL_PATCH="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux-patches" BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux.config" From d826f2bc9b3c92f632065d5a613daf19055f8b48 Mon Sep 17 00:00:00 2001 From: "renovate-hash-sync[bot]" Date: Wed, 9 Sep 2026 23:45:18 +0000 Subject: [PATCH 2/2] renovate-hash-sync: refresh companion hash(es) for this PR Recomputed from a freshly-fetched artifact: - driver/firmware/libchdr package pins: sha256sum of the github archive tarball at the new pinned owner/repo/ref (same "locally computed" practice this tree's own .hash file headers already document) - kernel pins (stable 6.18.y and the RT/beta 7.2 line): kernel.org's signed sha256sums.asc for each pin's own vN.x series. An -rc is never refreshed here -- no signed manifest exists for one - ip7z/7zip pins (lzma-sdk, 7zip): sha256sum of the release ASSET for the new version (upstream publishes no checksums at all -- see package/lzma-sdk/lzma-sdk.hash's header), PLUS the files each package's *_LICENSE_FILES names, hashed from that same asset. A changed license file is refreshed AND diffed into the step log with a ::warning:: -- read that diff before merging; it is the only thing standing between an automated hash refresh and a silent relicense - sdcard payload pins (update_all.sh, wifi.sh): sha256 + size of the raw file at the new pinned commit, rewritten in place in scripts/fetch-sdcard-payload.sh - Buildroot pin (BUILDROOT_SHA256, root Makefile): transcribed from buildroot.org's GPG-signed release manifest (buildroot-.tar.gz.sign) -- the same signed file `make buildroot-showsig` prints, never a locally-computed sha256sum of the tarball (that remains forbidden; see the Makefile's own header comment) - azcopy pin: REBUILT, not fetched. Buildroot's own support/download/go-post-process re-ran `go mod vendor` over the newly pinned tag with the Go version the pinned Buildroot tree pins, and the resulting azcopy--go2.tar.gz was hashed -- the only way this value can be derived, since no URL serves that file (see package/azcopy/azcopy.hash's header). LICENSE and NOTICE.txt were re-hashed from the same tarball - golden config hashes (configs/fragments/golden.sha256): on a Buildroot bump only, the target branch's own scripts/check-config-fragments.sh --update-golden was run against the freshly unpacked (hash-verified) Buildroot tree and the new version's lines recorded -- never a rewrite of lines that already existed (docs/buildroot-config.md section 11) --- board/mister/de10nano/patches/linux/linux.hash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/board/mister/de10nano/patches/linux/linux.hash b/board/mister/de10nano/patches/linux/linux.hash index bd274e0d..a2428162 100644 --- a/board/mister/de10nano/patches/linux/linux.hash +++ b/board/mister/de10nano/patches/linux/linux.hash @@ -36,7 +36,7 @@ # A kernel bump (manual, or Renovate under P4.7) MUST update this line from the # signed manifest for the new version, or the build will fail closed -- which is # the intended behaviour. -sha256 ae826f33111fea6f1d279dde7299d7463c8dfd204aeb75a8fb5432bc60a28191 linux-6.18.49.tar.xz +sha256 d2fc041dab4e11d9645e3ba53be058faa52b8ce28a8a97c889bb2cacee170461 linux-6.18.50.tar.xz # WHERE THE RT / BETA KERNEL HASH COMES FROM -- as of 2026-08-17, the SAME # signed-manifest rule as the stable pin above. This entry belongs to the RT