Upgrading from 4.x? 5.x needs Node 22.14+ or 24+; Node 20 and 23 are unsupported. On Node 20, npm warns and still installs unless engine-strict is set; the database engine will not load. Read the guide.

launch release memory

ShieldCortex 5.12.0: Embedding Model Cache Settings, Config Re-sign, Dashboard Update Check Switch

DS
Drakon Systems · 22 October 2026

ShieldCortex 5.12.0 was released on 22 October 2026. It is a minor release on 5.11.0: it adds a new CLI path, a new config flag and key, and new environment variables. With none of the new settings set, embedding model loading and the dashboard update check behave as in 5.11.0, except where a host already exports HF_ENDPOINT. Action Guard stays off by default in the shared ShieldCortex config.

What shipped

Embedding model cache, offline and mirror settings (#632). Three opt-in settings let the local embedding model load from a relocated cache root (SHIELDCORTEX_MODEL_DIR), run offline from a pre-seeded cache (SHIELDCORTEX_EMBEDDINGS_OFFLINE=1), or download from a validated mirror (HF_ENDPOINT). Invalid settings fail closed: embeddings stay off and shieldcortex doctor names the variable, with no fallback directory or host. This covers the embedding model only and is not a product-wide offline mode: update checks, the dashboard, cloud sync, configured integrations and the optional review-copilot and judge models are separate.

Config re-sign recovery path (#647). For a config.json that fails its signature check, shieldcortex config --resign previews first and writes nothing. Confirming with the sha256 it printed re-signs the parse of exactly those bytes, keeps a timestamped byte backup and records a config_resigned audit row. Re-signs that would loosen Action Guard keys no verified root-owned policy lock covers are refused. The signature is still a corruption detector, not tamper protection.

Dashboard update check can be turned off (#631). Operators can turn off the dashboard’s automatic npm registry version lookup with shieldcortex config --dashboard-update-check false or SHIELDCORTEX_SKIP_UPDATE_CHECK=1. It stays on by default.

Release hygiene. The npm release workflow refuses to publish when the v<version> tag points at a different commit from the one being built (#881); this is a maintainer release check. A test-only change pins the defence pipeline entry-point table (#861) and changes no shipped code.

Upgrade to 5.12.0

npm install -g shieldcortex@5.12.0

Four things to know before you upgrade:

  • An HF_ENDPOINT you already export now applies to the embedding model. ShieldCortex validates it and downloads the embedding model from that endpoint. If it fails validation (for example plain http to a non-loopback host), embeddings stay off until it is fixed or unset, and doctor names the variable.
  • New config --resign flow for a config.json that fails its signature check. Run the preview first: it prints the verdict, the sha256 of the current bytes and the names of settings that would leave the strict posture, and writes nothing. Confirm with that sha256 only after you have reviewed the file. Restoring a backup whose signature verifies, or rebuilding through the setters, still works.
  • The dashboard update check can be turned off. It stays on by default. Turning it off stops that one lookup only: shieldcortex update, the dashboard’s Update button and cloud sync are unchanged.
  • Maintainers: the version tag must be on the release commit. Tag the merged release commit before publishing.

Read the changelog →

Built by Drakon Systems.