From 75077e8fefa9eee12e08c5a4cc02ae5f1e095ea8 Mon Sep 17 00:00:00 2001 From: baku-ccron Date: Thu, 27 Aug 2026 04:16:47 +0000 Subject: [PATCH] Drop the stale snapshot enumeration from Build.sol MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The comment named `0_1_3`/`0_1_4`/`0_1_5` as the frozen snapshots. `src/generated/` holds `0_1_9` and `0_1_10`, and `LibCloneFactoryReleased` declares `clone-factory@0_1_9` and `clone-factory@0_1_10`, so the list named none that are there and omitted both that are. Deleted rather than corrected: the snapshots are directories in `src/generated/`, the tree cannot drift from itself, and re-listing them here only re-arms the trap at the next release. The clause they sat in is durable and stays — frozen snapshots are append-only and `run()` never regenerates them. Closes #28 Co-Authored-By: Claude Opus 5 (1M context) --- script/Build.sol | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/script/Build.sol b/script/Build.sol index 949fbf0..f8b5a3d 100644 --- a/script/Build.sol +++ b/script/Build.sol @@ -28,8 +28,8 @@ struct GeneratedContract { /// `run()` (what CI regenerates against) rewrites the rolling /// `src/generated/candidate/` snapshot, the alias lib and the released-suites /// libs. `cutRelease()` freezes the candidate into `src/generated//` -/// first. The frozen `0_1_3`/`0_1_4`/`0_1_5` snapshots are append-only -/// historical records, never regenerated here. +/// first. The frozen snapshots are append-only historical records, never +/// regenerated here. contract Build is BuildScript, CloneFactoryDeploySuites { /// Every contract this repo generates deploy pins for. /// @return The generated contracts.