From 5c8a6e2c40cc0685671e59ffc030f9c69d7adb81 Mon Sep 17 00:00:00 2001 From: "prompt.ac/@jeffrey" Date: Mon, 28 Sep 2026 17:42:29 -0700 Subject: [PATCH] aesel.json and easel.json stop being tracked They are pack.mjs output and .gitignore already says so, but the rename (7e75aed13c) force-added them at 0.8.0. Any reset of lith's checkout without a re-pack after it (a rollback, or a second deploy landing in the same minute) put that stale feed back: after e4208fb385 production advertised Aesel 0.8.0 beside a 0.8.18 tarball, and ac-deploy's check caught it. Untracked, a reset can only remove them, and the pack that follows every deploy writes them fresh. --- system/public/aesel.json | 6 ------ system/public/easel.json | 6 ------ 2 files changed, 12 deletions(-) delete mode 100644 system/public/aesel.json delete mode 100644 system/public/easel.json diff --git a/system/public/aesel.json b/system/public/aesel.json deleted file mode 100644 index b5d2c625b0..0000000000 --- a/system/public/aesel.json +++ /dev/null @@ -1,6 +0,0 @@ -{ - "version": "0.8.0", - "sha256": "eddbecccf7f00e9de91a471408ee0727672d81991ab33ce4553959173ef123a4", - "bytes": 892527, - "tarball": "/aesel.tar.gz" -} diff --git a/system/public/easel.json b/system/public/easel.json deleted file mode 100644 index 7ca50df9e3..0000000000 --- a/system/public/easel.json +++ /dev/null @@ -1,6 +0,0 @@ -{ - "version": "0.8.0", - "sha256": "eddbecccf7f00e9de91a471408ee0727672d81991ab33ce4553959173ef123a4", - "bytes": 892527, - "tarball": "/easel.tar.gz" -} -- 2.51.2