From 57ed7d8c2ea5b42eedc79b21fd482095f8af2fbf Mon Sep 17 00:00:00 2001 From: Ryanmello07 <67509637+Ryanmello07@users.noreply.github.com> Date: Sat, 22 Aug 2026 00:47:27 -0700 Subject: [PATCH] extension: bump the submodule past the lint fixes The extension leg of the CI has been red since it was added, and it is not the workflow's fault: this repo pinned extension at 8f75f07d8b, which predates urnetwork/extension#36. `npm run lint` fails there with 12 errors -- 9 no-explicit-any, an unused parameter, and two react-hooks/refs violations, one of which was a real correctness bug (refs assigned during render, feeding a ConnectionManager built once with [] deps that invokes the auth thunk from timers). #36 fixed all twelve and merged upstream, but a submodule pin does not follow a merge in the component repo. So CI kept building the pre-fix tree and kept reporting the same twelve errors. Worth noting as a pattern rather than a one-off: this is the second time a pin lag has produced a red leg that looked like a CI defect. The Arch package leg was the first -- it warned and skipped for two runs because packaging/make-arch.sh did not exist at the pinned linux commit. Now that every component repo builds and tests itself on push, the build repo's pins are the thing most likely to go stale, and a stale pin presents as a failure in whatever the pin feeds. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01MAXFxG1EK4jTxQ1iW73BUr --- extension | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extension b/extension index 8f75f07d..660e05e3 160000 --- a/extension +++ b/extension @@ -1 +1 @@ -Subproject commit 8f75f07d8bd0fdfea983f8ed9453807914f25177 +Subproject commit 660e05e39d965e43e3c27ca099cd167376ba6fce