Apart from a bunch of random bugfixes, this release introduces a new uniqueness constraint bases on a sha256 digest to the collection version content. In order to comply with our goal to allow for zero downtime upgrades, this “feature” will not yet have any user visible impact, but instead prepare the database to make the actual switch of the uniqueness constraint in the next release. In case you upgrade Pulp without downtime, you should run pulpcore-manager datarepair-ansible-collection-sha256 after upgrading all components to 0.23.* and before upgrading any to the yet to be created 0.24.* release. 0.24 will then ship with better isolation of collection content uploaded by different users into their personal ansible repositories.
2 Likes