🚨 nightly release failing

[github-actions]

Release Failure — v0.3.35-nightly.20260721

The nightly release failed.

Failed jobs: test

• test: failure
• release: success
• helm-release: skipped

Workflow run: https://github.com/kubestellar/console/actions/runs/29805735617

---

⚠️ Closure policy

Do not close this issue until the Release workflow passes on main.
Fixing the failing test is necessary but not sufficient — the nightly
must actually succeed and produce a release before this issue is resolved.
Verify with: gh run list --repo kubestellar/console --workflow Release --limit 3

Auto-created by the release workflow. Subsequent nightly failures within 48h will append to this issue instead of opening a duplicate.

[clubanderson]

Same root cause as #21353. Test job failed because of 3 stale test assertions on main after PR #21318. Fixes merged this cycle:

• 🌱 fix: update CanIChecker tests for auto-select cluster behavior #21344, 🐛 fix: update EnterpriseComplianceCards test for semantic color tokens #21346, [scanner] 🐛 fix: update CreateNamespaceModal test for auto-select cluster #21354, 🐛 fix: remove unused error binding blocking build-gate on main #21345

Leaving open per closure policy until next successful nightly release on main.

[clubanderson]

Root Cause Analysis

The nightly release (test job) failed at commit 2ea59dd25368caf5299df74b284c8445109b7337 because of a new ESLint violation introduced in web/src/components/enterprise/EnterpriseLayout.tsx.

The lint-warning-gate step (npm run lint:check) detected:

❌ New lint violations detected:
   @typescript-eslint/no-unused-vars (1 new) in src/components/enterprise/EnterpriseLayout.tsx
   src/components/enterprise/EnterpriseLayout.tsx:182:14 — 'error' is defined but never used.
   Allowed unused caught errors must match /^_/u.

Line 182 had } catch (error) { where the error binding was never referenced inside the block. All other catch blocks in this file already use the empty } catch { form (optional catch binding, valid since TypeScript 4.0).

Fix

The fix — changing catch (error) → catch { — is already present in the current main HEAD at commit fd4a258088cb7fd38e9a6bfb7c67fe881e366f05. The file blob SHA changed from 151079e8c1f0343d2c897e801df0eaa3b63dcab1 (broken) to f9b6d5092f76e3bf9371eed15b89b3707a78604c (fixed).

The next scheduled nightly release (tomorrow, 05:00 UTC) should pass. No additional action is required — this issue can be closed once that run succeeds.

---

Analysis by scanner agent

[clubanderson]

Scanner investigation complete — PR opened

Root cause confirmed: The test job in run #29805735617 failed at the Lint frontend step (npm run lint:check), not go test ./.... The Go tests passed.

Specific violation: @typescript-eslint/no-unused-vars — unused catch (error) binding in EnterpriseLayout.tsx:182 introduced by #21342.

All code fixes are already merged to main:

• 🐛 fix: remove unused error binding blocking build-gate on main #21345 — dropped the unused binding (core lint fix)
• 🌱 fix: update CanIChecker tests for auto-select cluster behavior #21344, 🐛 fix: update EnterpriseComplianceCards test for semantic color tokens #21346, [scanner] 🐛 fix: update CreateNamespaceModal test for auto-select cluster #21354 — fixed stale test assertions from [scanner] fix: nightly unit-test regression #21318

PR #21360 adds a regression guard: documents the catch { } convention in eslint.config.js and improves the lint-baseline-check.mjs error message with a targeted tip, so future contributors get immediate guidance instead of a cryptic baseline-count failure.