-
RouterForge 0.9.0 Stable
released this | 727 commits to main since this release
RouterForge 0.9.0
🇷🇺 Русский
RouterForge 0.9.0
Что нового
- App Center получил завершённую Registry / Manifest Platform: bundled manifests стали источником истины для интеграций, local/private sources получили namespaced identity, preview + explicit add с SHA-256 и conservative trust-модель.
- Private Forgejo оформлен как hot-backup Git authority с fail-closed promotion/restore procedure; GitHub остаётся primary и автоматический Forgejo -> GitHub sync запрещён.
- Shared Safety Engines объединяют path validation, atomic file/config writes, swap/rollback и bounded command execution для пользовательских control paths.
- App Center получил Jobs + History, сохранение технических логов, безопасное открытие локальных Web UI и устойчивый переход между каналами.
- Network Tools существенно расширен: Route Inspector и runtime/UI диагностика маршрутов и сетевого состояния.
Исправления
- DNS health переведён с накопительных lifetime-счётчиков на rolling window: старые ошибки больше не держат резолвер в вечном DEGRADED, NXDOMAIN информационный, а текущая причина проблемы показывается по конкретному резолверу.
- Management same-origin actions работают при отключённой авторизации RouterForge; при включённой авторизации root-session остаётся обязательной. Cross-origin, exact-target confirmations и process/path guards сохранены.
- Обновления между каналами выполняют модули до Core и Core последним; transient empty/invalid JSON во время рестарта Core обрабатывается явно.
- Исправлены module UI caching/revisioning, history workspace, resolver details drawer и thermal sensor discovery/presentation на Keenetic.
Совместимость
- Компоненты версионируются независимо: Core 0.9.0, DNS 0.8.1, Admin 0.8.1, Monitoring 0.8.0, Network Tools 0.9.0, Profiling 0.7.1.
- DNS/Admin/Monitoring/Network Tools требуют Core 0.9.0; неизменённый Profiling сохраняет min_core_version 0.7.1.
- Stable остаётся multiarch: aarch64-3.10 production; mipsel-3.4 и mips-3.4 experimental.
Технические изменения
- Stable 0.9.0 готовится относительно Stable 0.8.0; между базовым Stable SHA и release-prep базой накоплено 70 коммитов.
- Stable promotion выполняется только из exact Dev SHA после успешного FULL RELEASE с publish_beta=false.
- Публикуются 6 компонентов × 3 target = 18 IPK; rolling routerforge-stable обновляется только после валидации exact promotion artifact.
Текущие версии компонентов
Компонент Версия RouterForge Core 0.9.0RouterForge DNS 0.8.1RouterForge Control 0.8.1RouterForge Monitoring 0.8.0Profiling 0.7.1Установка
Свежая установка RouterForge Stable:
/opt/bin/opkg update && /opt/bin/opkg install curl && /opt/bin/curl -fsSL https://github.com/Fifth-Ace/routerforge/releases/download/routerforge-v0.9.0/routerforge-stable-bootstrap.sh | shСборка и проверка
- Версия RouterForge:
0.9.0 - Архивный релиз:
routerforge-v0.9.0 - Коммит:
f32520e - Release index:
routerforge-stable-index.json - Bootstrap:
routerforge-stable-bootstrap.sh
🇬🇧 English
RouterForge 0.9.0
What's new
- App Center now includes the completed Registry / Manifest Platform: bundled manifests are the integration source of truth, local/private sources use namespaced identity, explicit preview/add with SHA-256, and a conservative trust model.
- Private Forgejo is documented as a hot-backup Git authority with fail-closed promotion/restore; GitHub remains primary and Forgejo -> GitHub synchronization is never automatic.
- Shared Safety Engines centralize path validation, atomic file/config writes, swap/rollback and bounded command execution for user-facing control paths.
- App Center now has Jobs + History, persisted technical logs, safe local Web UI opening and hardened channel transitions.
- Network Tools received a substantial Route Inspector and runtime/UI diagnostics expansion.
Fixes
- DNS health now uses rolling windows rather than lifetime counters; historical errors no longer keep resolvers permanently DEGRADED, NXDOMAIN is informational, and current problems are attributed per resolver.
- Management same-origin actions work when RouterForge authentication is disabled; auth-enabled deployments still require a root session. Cross-origin, exact-target and process/path guards remain.
- Channel updates apply modules before Core and Core last; transient empty/invalid JSON during Core restart is handled explicitly.
- Module UI caching/revisioning, history workspace behavior, resolver details and Keenetic thermal discovery/presentation were corrected.
Compatibility
- Components are independently versioned: Core 0.9.0, DNS 0.8.1, Admin 0.8.1, Monitoring 0.8.0, Network Tools 0.9.0, Profiling 0.7.1.
- DNS/Admin/Monitoring/Network Tools require Core 0.9.0; unchanged Profiling keeps min_core_version 0.7.1.
- Stable remains multi-arch: aarch64-3.10 production; mipsel-3.4 and mips-3.4 experimental.
Technical changes
- Stable 0.9.0 is prepared relative to Stable 0.8.0; 70 commits separate the Stable base SHA from the release-prep base.
- Stable promotion is allowed only from an exact Dev SHA after successful FULL RELEASE validation with publish_beta=false.
- Stable publishes 6 components × 3 targets = 18 IPKs; the rolling routerforge-stable channel is updated only after exact promotion artifact validation.
Current component versions
Component Version RouterForge Core 0.9.0RouterForge DNS 0.8.1RouterForge Control 0.8.1RouterForge Monitoring 0.8.0Profiling 0.7.1Installation
Fresh RouterForge Stable install:
/opt/bin/opkg update && /opt/bin/opkg install curl && /opt/bin/curl -fsSL https://github.com/Fifth-Ace/routerforge/releases/download/routerforge-v0.9.0/routerforge-stable-bootstrap.sh | shBuild and verification
- RouterForge release:
0.9.0 - Immutable release:
routerforge-v0.9.0 - Commit:
f32520e - Release index:
routerforge-stable-index.json - Bootstrap:
routerforge-stable-bootstrap.sh
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads