seed: bump to 37b066fa9489 #55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "automated/seed-bump-37b066fa9489"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated seed-bump proposal from
tools/bump-seed.sh— the anthraxx commit signature was verified againstkeys/anthraxx.gpg.Review before merging: confirm the new seed targets the kernel version we build (the seed may legitimately lag) and that the hardening delta below is acceptable. Merging only updates the pinned config seed; the next kernel tag picks it up, and
build-kernel.yml's fidelity assertion + hardening-drift guard run on that build.The automated seed bump pinned anthraxx's 7.2.5.hardened1-1 config into configs/seeds/7.1.toml, which validate.yml's seed-pins-well-formed job rejects as a cross-series pin (tag series != filename series). Rather than mark 7.1 as a cross-series stopgap, stand the 7.2 line up properly per configs/lines.toml / docs/operators/config-architecture.md: - configs/seeds/7.1.toml: restored to its last same-line pin (7.1.9.hardened1-1), unchanged from main. - configs/seeds/7.2.toml: new same-line seed, populated by tools/bump-seed.sh --pin-file configs/seeds/7.2.toml 7.2.5.hardened1-1 (commit signature verified against keys/anthraxx.gpg; commit + sha256 match the bot's run). Header prose written for 7.2; kconfig delta vs the 7.1.9 seed shows no hardening-relevant changes. - configs/upstream-seed.toml: symlink repointed -> seeds/7.2.toml. - configs/lines.toml: stable line series/seed -> 7.2. - docs: current-line note updated. The first v7.2.x build has no same-line drift baseline in releases/, so build-kernel.yml will log the documented "hardening-drift guard SKIPPED" warning for it; subsequent 7.2 builds baseline against that release. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>