Minimum Package Age & Version Fallback
Malware is always blocked, no matter its age or which version was requested. The behavior below only applies to packages that are not identified as malware.
The Minimum Package Age policy sets how long a version must have existed before it can be installed. For example, with a minimum age of 24 hours, any version published less than 24 hours ago is considered too new.
What happens when a version is too new depends on how the install was requested: for a specific version or for the latest version.
Specific version requested
When an install pins an exact version, Aikido can only accept or reject that exact version. There is nothing to fall back to.
Version meets the minimum age β the install is allowed.
Version is too new β the install is blocked, and an event is shown so you can see what was held back.
Latest version requested
When an install asks for the latest version, Aikido has room to fall back. Instead of blocking outright, it returns the newest version that still meets the minimum age.
Latest version meets the minimum age β the latest version is returned.
Latest version is too new β Aikido falls back to the newest version that meets the minimum age, and that version is returned instead.
This keeps installs working while still holding back versions that are too new to have been vetted by the community.
Decision flow
Need a specific new version that the minimum age policy is holding back? Add an exception and set its Minimum Package Age to "No Minimum". See Configuring Installation Policies.
Last updated
Was this helpful?