From e54adac104a6e0fde649d0f6630e69083c41a4f5 Mon Sep 17 00:00:00 2001 From: Ronald Tse Date: Wed, 11 Nov 2026 14:27:48 +0800 Subject: [PATCH] docs: release-assets pipeline dead since <= v3.1.0 - retire-or-revive is an owner decision (recorded with evidence) --- TODO.all-sys/INDEX.md | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/TODO.all-sys/INDEX.md b/TODO.all-sys/INDEX.md index a1911c5..695350d 100644 --- a/TODO.all-sys/INDEX.md +++ b/TODO.all-sys/INDEX.md @@ -116,4 +116,30 @@ was re-dispatched immediately — **green** (run 42942594684). | interscript (crates.io) | 0.2.0 | crates.io trusted publishing (publish.yml) | max_version 0.2.0; run 42942246925 green — required two CI-mechanics fixes (#13 path→version rewrite with a proven published-form build; #14 `--allow-dirty`, the rewrite IS the dirty state) | | site catalogue | — | interscript.github.io PR #230 (merged) | 428/428, zero drops, `^5.11.0` | - interscript-py stays PyPI-locked (owner gate). \ No newline at end of file + interscript-py stays PyPI-locked (owner gate). +## Ruby release-assets pipeline: dead since ≤ v3.1.0 (owner decision) + +The `release-assets` workflow (vis_json.zip + metadata.json.zip per +release) failed on the v3.4.0 tag with two stacked causes: upstream +`thedoctor0/zip-release` retagged (v0.7.6 → 0.7.6; fixed in +interscript-ruby PR #838 with a dispatch tag input), and beneath that +the job runs the FROZEN interscript/ monorepo's `ruby/` tree — its +`generate_visualization_json` rake task calls +`Interscript::Node::Stage#to_visualization_array`, undefined in the +workflow's load path (and the layout predates the gem split: the +rake's `../maps` path source isn't even checked out). + +History: **no release since at least v3.1.0 carries these assets** +(v3.1.0/v3.2.x/v3.3.0/v3.4.0 all verified via the releases API) — +three releases shipped without anyone missing them; the Astro site +renders rule charts from the catalogue, not this JSON. + +OWNER DECISION (retiring a release-asset pipeline): either retire the +workflow (it ships artifacts nobody has received since 3.1.0), or +revive it properly — port `generate_visualization_json` to the gem's +own Rakefile (the gem already carries `visualize/json.rb` and +`generate_metadata_json`), check out ../maps in the workflow, and +teach the visualization the ISC-WF-1 nodes (Ruleset / Rule::Use / +LanguagesDecl / Sub#when_languages). PR #838's dispatch-tag input +supports either path. The v3.4.0 release is NOT missing anything it +ever had in the 3.x era.