Versions and lifecycle
Numspot operates its Container Registry instances with stable versions of Harbor that benefit from active monitoring of security patches, in compliance with the security requirements applied to the service.
Supported versions
The following minor versions are supported:
- Harbor 2.13
- Harbor 2.14
This scope covers the stable versions actively maintained by the Harbor project, with continuous monitoring of security advisories.
When you create a Container Registry instance, the most recent version is selected by default. For more information, see Create a Container Registry.
Security patch monitoring
The images used for Container Registry instances include:
- patch updates applied regularly to fix bugs and security flaws;
- active monitoring of critical and high vulnerabilities.
Patch updates are applied automatically by Numspot and require no action from the customer. They concern only patch versions (for example, 2.14.0 to 2.14.1), without any change to data compatibility.
To obtain information about the applied versions or recent patches, contact Numspot support.
Version lifecycle
Support policy
| Version | Support status | Estimated Numspot end of support |
|---|---|---|
| 2.13 | Active | October 2026 |
| 2.14 | Active | February 2027 |
The support status is aligned with the Harbor project announcements. Numspot follows the Harbor policy for the support of minor versions.
End-of-support notification
Numspot notifies its customers several months before the end of support of a minor version. This notification allows customers to plan the update to a more recent version.
Minor updates
Minor updates (for example, from Harbor 2.13 to Harbor 2.14) trigger an update of the Container Registry instance. Numspot recommends that you test the compatibility of your workflows before proceeding with a minor update.
The version update may cause a temporary unavailability of the Container Registry instance (UPGRADING state). It is the customer's responsibility to verify that their workflows are compatible with the new version before any migration.