Agent Versioning and Support
Agent Versioning
The Automox agent follows industry standards for Major, Minor, and Patch.
Major Version Number
In general, a major version means a release of an Automox agent that contains substantial changes in functionality, code, or compatibility and incorporates any existing previous release or fixes. Unless otherwise specified for a particular product, a version is designated by the number to the left of the decimal point such as 1.0, 2.0, 3.0, etc.
Minor Version Number
The minor version number means a release of an Automox agent which may contain minor new product functionality, code, or compatibility and incorporates any previous fixes since the last version. Unless otherwise specified for a particular product, a release is tied to the preceding version and is designated by a number to the right of the decimal point such as 1.1, 1.2, 1.3, etc.
Patch Version
The patch version number means a release of the Automox agent that includes defect fixes only since the last minor release. Unless otherwise specified for a particular product, the patch version is tied to the preceding Major. Minor version and is designated by the number to the right of the minor version number such as 2.1.12, 2.1.25, 2.1.37, etc.
Version Support Process / Policy
Support Scope
Automox defines Agent support and deprecation at the major.minor version level (for example, 4.2). Patch releases (for example, 4.2.14 or 4.2.37) inherit the lifecycle of their parent major.minor version and do not reset or extend support timelines.
Active Support
Each Automox Agent major.minor version is supported for at least 12 months from General Availability (GA).
During Active Support, Automox provides:
- Security updates
- Critical bug fixes
- Compatibility updates
- Standard technical support
End-of-Support/Life (EOS/EOL)
End of Support (EOS)
After the Active Support period, a version enters End of Support (EOS).
At EOS:
- Automox provides no further bug fixes or enhancements.
- Automox may provide security fixes at its discretion.
- Support may require upgrade as a prerequisite for investigation.
End of Life (EOL)
After EOS, a version proceeds to End of Life (EOL) following a defined deprecation window.
At EOL:
- The agent version is fully unsupported.
- Automox may prevent it from connecting to the Automox platform.
- Automox may enforce automatic upgrades where supported.
- Support and Engineering do not investigate issues.
Deprecation Timeline
Automox provides clear notice before EOS and EOL:
- At least 3 months’ notice before EOS.
- At least 6 months’ notice before EOL.
Automox calculates dates in whole calendar months, with EOS and EOL occurring at the end of the applicable month
Agent EOS/EOL List
| Agent Version | EOS Date | EOL Date |
|---|---|---|
| All versions < 2.0.28 | June 15, 2025 | October 15, 2025 |
| All versions between 2.0.28 and 2.1 | May 31, 2026 | August 31, 2026 |
| 2.1 | May 31, 2026 | August 31, 2026 |
| 2.2 | -- | -- |
| 2.3 | -- | -- |
| 2.4 | -- | -- |
| 2.5 | -- | -- |
| 2.6 | -- | -- |
