Project

Profile

Help

Issue #9442

closed

Deprecation status isn't synced correctly when retain_repo_versions=1

Added by fao89 about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 106
Quarter:

Description

If a repo with deprecated collections sync from a remote without deprecations, the repo will keep its deprecations regardless the new remote

Also available in: Atom PDF