From f5e3f70e91e0b2430363e43e1c1f849b471b8dda Mon Sep 17 00:00:00 2001 From: Yuanhao Li Date: Fri, 28 Aug 2026 13:29:58 +0200 Subject: [PATCH] ci: bump the gasp conformance pin to the lenient checker MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The pin sat at 08a60a2, which predates today's fix, so this job was still certifying yoagent against the 0.4-era strict fold: one dangling op aborted check 2 and the run reported a failure with no indication of which op or how many others would have folded fine. 795bb93 folds leniently and names what it skipped on the certificate, and also drops the build.rs whose Cargo.lock parsing printed "unknown" for exactly the kind of build CI does. Verified by running the job's own sequence locally against the new SHA before bumping — emit, clone, check — rather than finding out on main: 7/7 with no skips, since yoagent's emitted repo has no dangling ops. The lenient fold changes what happens when one appears; it does not lower the bar for a clean store. Records the bump protocol in the comment, since the previous one said only "pin" without saying what makes a bump safe. --- .github/workflows/ci.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index a2ba732..18634c7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -111,7 +111,12 @@ jobs: uses: actions/checkout@v4 with: repository: yologdev/gasp - ref: 08a60a2ee30d6bc065ffbadec34a7993dc109fdf # pin: checker changes must not break yoagent CI silently + # Pinned so a checker change cannot break yoagent CI silently — bump + # deliberately, after running the job's sequence locally against the + # new SHA. This one folds leniently (gasp#3): a dangling op is a note + # on the certificate, not an abort, so check 2 now reports what it + # skipped instead of failing the whole run at the first bad op. + ref: 795bb93449adb206236a97d45d4dd674c0aae862 path: gasp-checker - name: Run conformance checker against a fresh clone (true restore) run: |