From e8009622b2d251e1fb317e2866435132fc7874d7 Mon Sep 17 00:00:00 2001 From: Daniel Rossier Date: Fri, 13 Nov 2026 18:20:54 +0100 Subject: [PATCH] release: v1.1.0 CHANGELOG entry, the Maintained versions table (1.1 current stable, 1.0 in maintenance) and IB_VERSION_FALLBACK for the v1.1.0 minor release: the SO3 recipes (#68), the manifest-based updiff (#64/#66, #67, #70) and the platform-switch and deploy fixes. --- CHANGELOG | 42 ++++++++++++++++++++++++++++++++++++++++++ README.md | 3 ++- scripts/ibversion.sh | 2 +- 3 files changed, 45 insertions(+), 2 deletions(-) diff --git a/CHANGELOG b/CHANGELOG index 6b1346e8f..44731e81d 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,4 +1,46 @@ +v1.1.0 (13 nov 2026) + +Minor release, the first of the release/v1.1 line: Infrabase builds SO3 +again, updiff only folds what was really edited, and the deploy and +platform-switch paths are fixed. + + • SO3 recipes. Infrabase builds SO3 as well as Linux: the kernel, + usr-so3, its musl 1.2.6 toolchain and bsp-so3, standalone or as an + AVZ guest, on virt64 and virt32. QEMU's virt machine carries the + so3 devices (absolute pointer, LAN9118) and st.sh passes a LAN9118 + NIC, which a Linux guest ignores. U-Boot now takes virt64_defconfig + on every virt64 chain, the bare Linux one included. (#68) + + • updiff detects edits from the attach manifest instead of diffing + every patched file against pristine: after a git pull bringing new + patches, an updiff about an unrelated file no longer reverts them. + Successive patches of one edited file are merged, an emptied patch + goes away, and updiff refuses to write when the series changed + under the tree. It folds edits into every series a recipe applies, + caps the number of new files (IB_UPDIFF_MAX_NEW) and refuses BSP + recipes. (#64/#66, #67, #70) + + • Platform switch: buildroot reconfigures, and drops its previous + output, when IB_PLATFORM or its defconfig changes, and the user + space CMake cache is wiped on an architecture change. Switching + virt64 to virt32 used to fail on a missing rootfs.cpio. (#61) + + • Deploy: the rootfs partition is emptied before the rootfs goes onto + it, so files the build no longer produces do not survive (#65); the + user space is copied without imposing the builder's ownership on + /, /etc, /usr and /root (#52); only the storage image's loop + devices are detached (#66). + + • Build: avz refetches when its SRCREV or patch set changes, the + buildroot make is skipped while nothing changed, 32-bit kernels + build with ARCH=arm, and linux/rootfs/images/initrd.cpio points to + the board's tracked initrd (#63, #66). + + • The tezi-custom sources needed by recovery-edgem.sh are committed + (#69), and the documentation shows the release under the sidebar + title (#62). + v1.0.1 (2 oct 2026) Patch release on the release/v1.0 line: four fixes to v1.0.0. diff --git a/README.md b/README.md index 6bbaff495..5695e91f2 100644 --- a/README.md +++ b/README.md @@ -126,7 +126,8 @@ land there and are tagged as patch releases. | Line | Branch | Latest release | Status | |------|--------|----------------|--------| -| 1.0 | [`release/v1.0`](https://github.com/smartobjectoriented/infrabase/tree/release/v1.0) | [v1.0.1](https://github.com/smartobjectoriented/infrabase/releases/tag/v1.0.1) | Current stable | +| 1.1 | [`release/v1.1`](https://github.com/smartobjectoriented/infrabase/tree/release/v1.1) | [v1.1.0](https://github.com/smartobjectoriented/infrabase/releases/tag/v1.1.0) | Current stable | +| 1.0 | [`release/v1.0`](https://github.com/smartobjectoriented/infrabase/tree/release/v1.0) | [v1.0.1](https://github.com/smartobjectoriented/infrabase/releases/tag/v1.0.1) | Maintenance | See all versions on the [Releases page](https://github.com/smartobjectoriented/infrabase/releases). diff --git a/scripts/ibversion.sh b/scripts/ibversion.sh index 474b16efe..eb01109f6 100755 --- a/scripts/ibversion.sh +++ b/scripts/ibversion.sh @@ -19,7 +19,7 @@ # # Usage: ibversion.sh -IB_VERSION_FALLBACK="1.0.1" +IB_VERSION_FALLBACK="1.1.0" _tree=$(cd "$(dirname "$(command -v -- "$0")")/.." && pwd)