Skip to content

Versioning

ThoseYearsBrian edited this page Jun 6, 2026 · 2 revisions

Aegis follows Semantic Versioning: vMAJOR.MINOR.PATCH.

Example: Aegis v3.0.1, where MAJOR=3, MINOR=0, and PATCH=1.

MAJOR (X) Version (Major Update): structural changes or compatibility changes. You must re-download the configuration and re-add your proxy nodes.

MINOR (Y) Version (Feature Update): new policy groups, new modules, or new capabilities. It is recommended to re-download the configuration and re-add your proxy nodes.

PATCH (Z) Version (Fix Update): rule fixes, annotation updates, or minor optimizations. No need to re-download the configuration; updating external resources is sufficient.

Important

It is recommended to enable 「Automatically reload if the profile was modified externally/remotely」. This option only applies to automatic reloading when the configuration file (.conf) changes. PATCH updates still require manually refreshing external resources (RULE-SET) to take effect.

Note

Current version: Aegis v2.0.0. Previous version: Aegis v1.3.4. This is a MAJOR update (MAJOR = 2). You must re-download the configuration and re-add your proxy nodes. External resources will be updated automatically.

Current version: Aegis v2.3.0. Previous version: Aegis v2.2.4. This is a MINOR update (MINOR = 3). It is recommended to re-download the configuration and re-add your proxy nodes. External resources will be updated automatically.

Current version: Aegis v3.3.4. Previous version: Aegis v3.3.3. This is a PATCH update (PATCH = 4). No need to re-download the configuration. You only need to refresh external resources.

Tip

As long as you re-download the configuration file (.conf) and re-add your proxy nodes, external resources will be updated automatically if the option 「Automatically reload if the profile was modified externally/remotely」 is enabled.

For PATCH version updates, you still need to manually refresh external resources (RULE-SET) for the changes to take effect.

Clone this wiki locally