In some cases, customers still prefer the complete removal of all subsequent manifests that are referenced by the previous list.manifest.json. Our recommended approach for managing list.manifest image overrides in this case is to activate the Tag Retention Logic on the repository configuration. This ensures that each list.manifest including all it’s references are treated as a single unit, and any overwrite beyond the configured retention limit will result in the complete removal of the oldest list manifest revision and all its sub-manifest tags and content.
It is important to note that applying this change to a repository with existing images will not retroactively remove them; it will only affect new content that is added moving forward.
Additionally, enabling Tag Retention will retain a minimum of one backup of the original list.manifest and all its subsequent tags. This ensures a safeguard for your previous state. In contrast, when Tag Retention is disabled, all subsequent tags are accumulated indefinitely unless managed through Cleanup Policies.
For more information on Tag Retention, see Use Tag Retention.