From d63f39e522f830b03afc0114589fc40dcebb2de1 Mon Sep 17 00:00:00 2001 From: SunnyRad Date: Thu, 12 Nov 2026 12:38:36 +0800 Subject: [PATCH] test(readme): pin install examples to released Core v1.3.1 0f1724a updated both READMEs' install pins from v1.3.0 to v1.3.1 and removed the release-candidate wording, but left the assertion in tests/readme-consistency.test.ts:104 at ['1.3.0']. Core v1.3.1 is published (draft=false, prerelease=false), so the test now fails on main itself and is inherited by every PR's plugin-tests job. Update the expected pin and its stale comment. One assertion, no README, product code, or other 1.3.0 reference touched. --- tests/readme-consistency.test.ts | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tests/readme-consistency.test.ts b/tests/readme-consistency.test.ts index 9b6e45b..bd862b6 100644 --- a/tests/readme-consistency.test.ts +++ b/tests/readme-consistency.test.ts @@ -99,7 +99,8 @@ test('install examples pin a version, not a moving branch', () => { for (const m of s.matchAll(/sessionFlow\.git@v(\d+\.\d+\.\d+)/g)) pins.add(m[1]); } assert.ok(pins.size > 0, 'at least one install example must pin a tag'); - // Core v1.3.0 is the released tag this plugin version was tested against. - // v1.3.1 is a release candidate and must NOT appear as a stable pin yet. - assert.deepEqual([...pins].sort(), ['1.3.0']); + // Core v1.3.1 is the released tag this plugin version was tested against; + // both READMEs' install examples were updated to pin it in 0f1724a ("docs: + // reflect Core v1.3.1 as released (README pins, pairing table, stale RC note)"). + assert.deepEqual([...pins].sort(), ['1.3.1']); });