EnerOS Release Overview

EnerOS (NengShu OS) is a Power/Energy-Native AgentOS for the power and energy domain, embedding power system domain knowledge, physical constraints, and operational logic into the OS kernel. The tech stack is Rust, currently comprising 56 crates and 7300+ test cases. This page aggregates the release notes for all EnerOS versions, allowing users to easily review new features, improvements, bug fixes, and upgrade guides for each version.

Version Evolution Overview

EnerOS version evolution follows a five-stage path: “Core Foundation → Architecture Expansion → Intelligence Enhancement → Industry Deepening → Maturity Optimization.” From v0.1.0 to v0.10.0 is the Core Foundation stage, building basic capabilities such as Cargo workspace, topology, power flow, constraints, Agent, equipment, time series, and protocols; v0.11.0 to v0.20.0 is the Architecture Expansion stage, completing platform-level capabilities including dual execution, multi-tenancy, digital twin, orchestration, security, high availability, SCADA, and zero trust; v0.21.0 to v0.30.0 is the Intelligence Enhancement stage, endowing Agents with swarm collaboration, physical constraints, grid analysis, operations automation, plugins, compliance, performance acceleration, distributed and cloud-native capabilities; v0.31.0 to v0.40.0 is the Industry Deepening stage, covering intelligent core, machine learning, forecasting, edge, IoT, digital twin enhancement, simulation, fault diagnosis, and energy trading; v0.41.0 to v0.47.0 is the Maturity Optimization stage, comprehensively reaching production-ready standards across six dimensions: performance, security, developer experience, documentation, ecosystem, and stability. Each version comes with a Git Tag and provides a detailed upgrade guide from the previous version.

Version naming follows the Semantic Versioning (SemVer) specification: 0.x.y indicates that long-term API stability is not yet committed, where y is a patch version and x is a feature version. During the 0.x phase, each feature version may introduce breaking changes, but must provide migration tools and upgrade guides. After 1.0.0 is released, long-term stability will be entered, and API changes will follow strict SemVer compatibility commitments.

Gathering energy at the hub, driving intelligent everything. EnerOS converges the energy of the power system at the hub of the AgentOS, driving the interconnected smart grid with a native agent architecture.

Version Timeline

The table below lists all 47 versions of EnerOS from v0.1.0 to v0.47.0, in reverse chronological order. Each version has its own release notes document; click the version number to view the full content.

Version Classification

The 47 versions of EnerOS are divided into five major stages by evolution phase, each with clear objectives and boundaries.

Stage 1: Core Foundation (v0.1.0 - v0.10.0)

• Time range: 2024-01 to 2024-10
• Version count: 10
• Core objective: Build the core architecture and foundational capability stack of EnerOS
• Key outcomes: Cargo workspace structure established (v0.1.0 Genesis), core crate foundation (v0.2.0 Foundation), grid topology data model (v0.3.0 Topology), Newton-Raphson power flow solver (v0.4.0 PowerFlow), physical constraint framework (v0.5.0 Constraint), Agent trait and message passing (v0.6.0 Agent), equipment model library (v0.7.0 Equipment), time series storage engine (v0.8.0 TimeSeries), protocol adapters (v0.9.0 Gateway), first milestone version (v0.10.0 Horizon)
• End marker: v0.10.0 Horizon as the first milestone version, with the foundational capabilities to provide external services

Stage 2: Architecture Expansion (v0.11.0 - v0.20.0)

• Time range: 2024-11 to 2025-06
• Version count: 10
• Core objective: Complete platform-level capabilities including dual execution, multi-tenancy, digital twin, orchestration, security, high availability, SCADA, and zero trust
• Key outcomes: Dual execution architecture (v0.11.0 DualExec), multi-tenant isolation (v0.12.0 Tenant), digital twin prototype (v0.13.0 Twin), Agent orchestration pipeline (v0.14.0 Pipeline), security guard (v0.15.0 Guardian), Raft high-availability consensus (v0.16.0 Raft), state estimation and operational insights (v0.17.0 Insight), SCADA integration (v0.18.0 Scada), IEC 61850 protocol (v0.19.0 IEC61850), zero-trust security (v0.20.0 ZeroTrust)
• End marker: v0.20.0 ZeroTrust established the zero-trust security baseline, completing platform-level capabilities

Stage 3: Intelligence Enhancement (v0.21.0 - v0.30.0)

• Time range: 2025-06 to 2025-12
• Version count: 10
• Core objective: Empower Agents with intelligent capabilities, covering swarm collaboration, physical constraints, grid analysis, operations automation, plugins, multi-language, compliance, performance, distributed, and cloud-native
• Key outcomes: Multi-agent swarm (v0.21.0 Swarm), physical constraint enhancement (v0.22.0 Physics), grid analysis (v0.23.0 Analysis), operations automation (v0.24.0 OpsAuto), plugin system (v0.25.0 Plugin), multi-language support (v0.26.0 Babel), compliance framework (v0.27.0 Comply), performance acceleration (v0.28.0 Turbo), distributed architecture (v0.29.0 Distributed), cloud-native (v0.30.0 Cloud)
• End marker: v0.30.0 Cloud completed the cloud-native transformation, with multi-region deployment capability

Stage 4: Industry Deepening (v0.31.0 - v0.40.0)

• Time range: 2026-01 to 2026-06
• Version count: 10
• Core objective: Deepen power industry domain capabilities, covering intelligent core, machine learning, forecasting, adaptive, edge, IoT, digital twin enhancement, simulation, fault diagnosis, and energy trading
• Key outcomes: Agent intelligent core (v0.31.0 Cortex), machine learning runtime (v0.32.0 ML), load and renewable energy forecasting (v0.33.0 Predict), adaptive regulation (v0.34.0 Adapt), edge computing (v0.35.0 Edge), ubiquitous IoT access (v0.36.0 IoT), digital twin enhancement (v0.37.0 TwinX), simulation engine (v0.38.0 Sim), fault diagnosis (v0.39.0 Diag), energy trading (v0.40.0 Trade)
• End marker: v0.40.0 Trade extended EnerOS capabilities from grid operation control to power market trading, covering both physical and market layers

Stage 5: Maturity Optimization (v0.41.0 - v0.47.0)

• Time range: 2026-06 to 2026-07
• Version count: 7
• Core objective: Comprehensively reach production-ready standards across six dimensions: performance, security, developer experience, documentation, ecosystem, and stability
• Key outcomes: Performance benchmarking system (v0.41.0 Bench), security audit and SBOM (v0.42.0 Audit), developer experience and hot reload (v0.43.0 DevEx), documentation system refactor (v0.44.0 Docs), ecosystem expansion and app marketplace (v0.45.0 Eco), stability enhancement (v0.46.0 Stable), brand convergence and NengShu OS (v0.47.0 Convergence)
• End marker: v0.47.0 Convergence completed the final convergence of brand and documentation, with 56 crates and 7300+ test cases, ready to enter the 1.0 candidate phase

Upgrade Path Recommendations

EnerOS allows breaking changes between versions during the 0.x phase, so upgrades must follow the correct path. Below are upgrade recommendations for common scenarios.

Upgrading from v0.40.0 to v0.47.0 (Latest)

It is recommended to upgrade version by version in order, handling the breaking changes of each version before upgrading to the next:

v0.40.0 → v0.41.0 → v0.42.0 → v0.43.0 → v0.44.0 → v0.45.0 → v0.46.0 → v0.47.0

Upgrade steps for each version:

1. Read the release notes of the target version to understand breaking changes
2. Run eneros-cli upgrade preflight for pre-check
3. Full backup: enerosctl backup create --type full
4. Update dependencies: cargo update
5. Handle breaking changes (following the migration guide in the release notes)
6. Run tests: cargo test --workspace
7. Verify upgrade: eneros-cli health check --full

Upgrading from v0.3x.x

There are significant architectural changes between v0.3x versions and v0.40.0. It is recommended to first upgrade to v0.39.0, then to v0.40.0, and finally follow the path above to upgrade to v0.47.0.

Cross-version Upgrade Risk

Pre-upgrade Checklist

• Read the release notes of the target version and all intermediate versions
• Confirm the Rust toolchain version meets requirements
• Full backup of the current system
• Rehearse the upgrade in a staging environment
• Prepare a rollback plan (executable within 30 minutes)
• Confirm sufficient maintenance window time
• Notify all relevant teams

Version Support Policy

EnerOS version support policy follows the principles below to ensure users have sufficient time for version migration in production environments.

Support Levels

Patch Version Strategy

After each feature version (0.x.0) is released, patch versions (0.x.1, 0.x.2, etc.) may be released to fix critical bugs and security vulnerabilities. Patch versions do not introduce breaking changes and can be safely upgraded.

Security Patch Response

LTS Preview

v0.48.0 will enter the “Long-Term Support Candidate” phase, and 1.0.0 will be released after v0.50.0, entering the LTS support cycle. LTS versions commit to at least 3 years of security patch and bug fix support, with API compatibility strictly following SemVer.

Version Lifecycle Diagram

v0.40.0  v0.41.0  ...  v0.46.0  v0.47.0  v0.48.0  ...  v0.50.0  1.0.0
  |         |              |         |         |              |       |
  |    Security Maintenance  No Longer Supported  Current Support  LTS Candidate       LTS Candidate    LTS
  |                                   ↑
  |                              Current latest version
  v0.40.0 - v0.45.0: Community Maintenance (until 1.0 release)

Related Documentation

• Architecture Design - Detailed EnerOS architecture
• Quick Start - 5-minute getting started guide
• Core Concepts - Power-Native design philosophy
• Upgrade Guide - Detailed upgrade process
• Security Advisories - Security vulnerability and patch records