From 98f6d1248606e0273a92c0387849ecf3acf803bf Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Mon, 14 Sep 2026 22:27:02 +0000 Subject: [PATCH 1/2] chore(deps): update dependency kernel-longterm-6.18 to v6.18.52 --- configs/mister_de10nano_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/mister_de10nano_defconfig b/configs/mister_de10nano_defconfig index 604a964..5dff06c 100644 --- a/configs/mister_de10nano_defconfig +++ b/configs/mister_de10nano_defconfig @@ -40,7 +40,7 @@ BR2_ROOTFS_POST_BUILD_SCRIPT="../../board/mister/de10nano/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="../../board/mister/de10nano/post-image.sh" BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_VERSION=y -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.51" +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.52" 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 28462791599ceecf43d6871ab3d3dd02363436d4 Mon Sep 17 00:00:00 2001 From: "renovate-hash-sync[bot]" Date: Mon, 14 Sep 2026 22:27:30 +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 --- 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 84641d8..23e8d1b 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 ba2f60f858bf4d1f929101faa356c93dc8b925b17aaa9f95eabd4627758df613 linux-6.18.51.tar.xz +sha256 2b69564f7d4fea0c859b1959ba33709ee6e9139bd100e30a853b57159a8221b8 linux-6.18.52.tar.xz # The RT / beta kernel's hash is NOT here any more: since ADR 0030 Phase C the # variant is package/linux-rt and its tarball hash lives in